Re: Antw: Re: Missing branches after clone

2019-05-15 Thread Philip Oakley
On 15/05/2019 09:45, Ulrich Windl wrote: reasoning for that. It's that you are missing the idea behind the "Branches that track the remote", which are local copies, but not YOUR branches. see below. I clone the GitHub test repo. I get (a copy of) it all (the rtb's). Git _creates_ a local branch '

Re: Antw: Re: Missing branches after clone

2019-05-15 Thread Ulrich Windl
>>> Philip Oakley schrieb am 15.05.2019 um 09:34 in Nachricht : > On 14/05/2019 12:49, Ulrich Windl wrote: >> Hi! >> >> The confusing part actually is for me: >> "git clone" does NOT "Clone a repository into a new directory", but "clone > the current branch into a new directory" (IMHO). >> So I w

Re: Antw: Re: Missing branches after clone

2019-05-15 Thread Philip Oakley
On 14/05/2019 12:49, Ulrich Windl wrote: Hi! The confusing part actually is for me: "git clone" does NOT "Clone a repository into a new directory", but "clone the current branch into a new directory" (IMHO). So I was surprised that I couldn't merge branches under the same name in the cloned "r

Antw: Re: Missing branches after clone

2019-05-14 Thread Ulrich Windl
Hi! The confusing part actually is for me: "git clone" does NOT "Clone a repository into a new directory", but "clone the current branch into a new directory" (IMHO). So I was surprised that I couldn't merge branches under the same name in the cloned "repository". Only "git clone --bare" actuall