git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Antw: Re: Missing branches after clone

From
UWUlrich Windl <ulrich.windl@rz.uni-regensburg.de>
Date
May 14, 2019, 11:49 UTC
Message-ID
<5CDAAB56020000A100031334@gwsmtp.uni-regensburg.de>
In-Reply-To
<0c9ec78a-9245-e1df-7ec6-a5d77d1a5261@iee.org>
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" actually seems to clone "the repository". I think this is very confusing to new users. At least I didn't quite get the reasoning for that.

Regards, Ulrich

>>> Philip Oakley <philipoakley@iee.org> schrieb am 14.05.2019 um 12:33 in
Nachricht <0c9ec78a-9245-e1df-7ec6-a5d77d1a5261@iee.org>:
Show 29 quoted lines
> Hi Ulrich,
> On 14/05/2019 11:12, Duy Nguyen wrote:
>>> Then I 
> foundhttps://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branch
> es  which handles the subject...
>>> But still the most common solution there still looks like an ugly hack.
>>> Thus I suggest to improve the man-pages (unless done already)
>> Yeah I expected to see at least some definition of remote-tracking
>> branches (vs local ones) but I didn't see one. Room for improvement.
> Yes, the 'remote tracking branch' name [RTB] is very 'French' in its 
> backwardness (see NATO/OTAN).
> 
> It is a 'branch which tracks a remote', and it is has the 'last time I 
> looked' state of the branch that is on the remote server, which may 
> have, by now, advanced or changed.
> 
> So you need to have the three distinct views in your head of 'My branch, 
> held locally', 'my copy of Their branch, from when I last looked', and 
> 'Their branch, on a remote server, in a state I haven't seen recently'.
> 
> Finding a better name for the "RTB", one with an easier cognitive load 
> for those trying to understand Git, would be an improvement.
> 
> Though there has been a similar issue with 'staging the index'. 
> Ultimately it is a new way of thinking about artefacts (perfect 
> duplicates, no originals, no master, no copies, just verification 
> hashes) so needs new terms and a difficult learning experience.
> -- 
> Philip
Previous: Philip OakleyNext: Philip Oakley
Message 8 of 13 in “Missing branches after clone”
  1. Ulrich WindlMay 14, 2019
  2. Duy NguyenMay 14, 2019
  3. Philip OakleyMay 14, 2019
  4. Duy NguyenMay 14, 2019
  5. Philip OakleyMay 14, 2019
  6. Duy NguyenMay 18, 2019
  7. Philip OakleyMay 19, 2019
  8. Antw: Re: Missing branches after cloneUlrich Windl, May 14, 2019
  9. Philip OakleyMay 15, 2019
  10. Ulrich WindlMay 15, 2019
  11. Philip OakleyMay 15, 2019
  12. Junio C HamanoMay 15, 2019
  13. Philip OakleyMay 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.