Note that there are some explanatory texts on larger screens.

plurals
  1. USMagnus O.
    primarykey
    data
    text
    plurals
    1. COSo if I would want to keep the master branch and development branch small I would always have to merge with the --squash and not the --no-ff flag? Any downsides of working like this? I see no real use of having all the history of the feature branches in the development and master branch? I will always keep the feature branches at the server for history if I would want to go back.
      singulars
    2. CO--squash seems to do what I want but I'm not sure if I want to do this anymore :) My repo is quite large because I have a lot of media in my project (movies, pdf etc) so whenever one media item changes I have a history of all the versions so the git repo groves fast. If I would start from scratch and work like it is descibed in the link with a master, development and feature branches. Would the master branch contain a log of all commits, even those that originated in the feature branch? So the master brash would actually be just a big anyway?
      singulars
    3. COOk, I will find smaller and more rects so that I will get one rect around each dot. Then I will measure the distance between the dots and if the distance is small enough I will combine the rects. This way I should be able to find the surrounding rect of almost the entire character. When I have a rect that is close enough I will use this to train the app and I will probably be able to match the letters. Sounds like a good approach?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload