On Sun, Aug 17, 2008 at 1:38 PM, Björn Steinbrink <B.Steinbrink@xxxxxx> wrote: > On 2008.08.17 12:23:57 -0700, Jakub Narebski wrote: >> Mike Gant <mwgant@xxxxxxxxx> writes: >> > I realize that I can create a new local branch that is based off the >> > desired branch: >> > >> > $ git-checkout -b master origin/master >> > >> > Is this the accepted method for obtaining the desired branch? >> >> You can use (with new anough Git) >> >> $ git checkout --track -b master origin/master >> >> to setup repository in such way that "git pull" on 'master' >> would know that it is meant to fetch from 'origin' and merge >> 'origin/master'. > > branch.autosetupmerge is set to true by default, so for remote branches > --track is the default anyway (since 1.5.5 IIRC). So only an old enough > git would actually require --track, unless you changed the config ;-) > > Björn > Thanks for your responses. I appreciate you guys taking the time to answer. After thinking about this, I still don't understand when I clone a repo why I will get the equivalent of whatever branch is active at the time of cloning? What was the process that led to this design decision? So that also got me thinking about work flows with git. Because of the way clone works it seems that you wouldn't want someone to clone your every day "work" repository? So do developers generally have a separate repository that they push to and others can clone? This repository may have only a 'master' branch (but probably others I seem to recall Junio describing other branches in the main git repository). Is this a 'normal' work flow? Thanks, Mike Gant -- 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
