Re: is this behaviour expected for "git clone --single-branch"?

2012-09-13 Thread Ralf Thielow
On Thu, Sep 13, 2012 at 8:45 PM, Junio C Hamano wrote: > Ralf Thielow writes: > >> # looking again to my branches > > Don't look at your branches, but look at how the refspecs are > configured by "git clone" in .git/config; I suspect we just write > the default 'refs/heads/*:refs/remotes/origin/*

Re: is this behaviour expected for "git clone --single-branch"?

2012-09-13 Thread Junio C Hamano
Ralf Thielow writes: > # looking again to my branches Don't look at your branches, but look at how the refspecs are configured by "git clone" in .git/config; I suspect we just write the default 'refs/heads/*:refs/remotes/origin/*' pattern. -- To unsubscribe from this list: send the line "unsubsc

is this behaviour expected for "git clone --single-branch"?

2012-09-13 Thread Ralf Thielow
Hi, I know people which have a separate directory for every branch. In this case it doesn't make sense to download the whole repo with all branches. So I guess the "--single-branch" option is the solution in that case!?! But I'm wondering about it's behaviour. # first clone the branch of the repo