Hi Daniel, With git the developer should ideally be doing their own development in topic branches. If this is the case then the developer would not have to do a pull before pushing their changes, since git has the facilities to track the and merge the changes across the branches.
if the other developer(s) is working on the master branch ( a big no-no IMHO ) instead, then a pull will be necessary before the push. HTH - Martin - On 2010-11-08, at 4:24 PM, Okalany Daniel wrote: > Hi All, > I'm trying to understand how to use git while doing team development. I've > used git while doing solo development, but if it needs to be more than a one > developer, is there a workflow/precautions other developers have to take? > E.g. If I pushed something to the "central" repository, after one of the > developers had already checkout, will they have to pull before pushing? Any > other info is welcome. > > Daniel. > > _______________________________________________ > LUG mailing list > [email protected] > http://kym.net/mailman/listinfo/lug > > LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > All Archives can be found at http://www.mail-archive.com/[email protected]/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The List's Host is not responsible for them in any way. > --------------------------------------- > _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ All Archives can be found at http://www.mail-archive.com/[email protected]/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
