Hello Junio, > You need to switch your mindset from centralized SVN workflow. Yes, we understood that and we are trying hard :) > The beauty of distributedness is that it redefines the meaning > of "to commit". In distributed systems, the act of committing > is purely checkpointing and it is not associated with publishing > the result to others as centralized systems force you to. > This is very nice actually and we absolutely understand what a commit means in the git world. Having the commit as a step before publishing is very helpful (although some concepts such as "staging for a commit" are still obscure as of now). > Stop thinking like "I need to integrate the changes from > upstream into my WIP to keep up to date." You first finish what > you are currently doing, at least to the point that it is > stable, make a commit to mark that state, and then start > thinking about what other people did. One particular situation in which this might not apply is when two people work very closely on the same feature (as mentioned by Steve Grimm in this thread) and one needs the changes made by the other. This often happens when starting a new project, as it is our case now :) Thank you, - Aghiles. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
