git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.org>
To: Duy Nguyen <pclouds@gmail.com>,
	Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Missing branches after clone
Date: Tue, 14 May 2019 11:33:05 +0100	[thread overview]
Message-ID: <0c9ec78a-9245-e1df-7ec6-a5d77d1a5261@iee.org> (raw)
In-Reply-To: <CACsJy8AX9Wp3W=d1=ozF9nZXGE1muooMf7fKCtdOOi1g8QRmig@mail.gmail.com>

Hi Ulrich,
On 14/05/2019 11:12, Duy Nguyen wrote:
>> Then I foundhttps://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branches  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

  reply	other threads:[~2019-05-14 10:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  9:41 Missing branches after clone Ulrich Windl
2019-05-14 10:12 ` Duy Nguyen
2019-05-14 10:33   ` Philip Oakley [this message]
2019-05-14 10:53     ` Duy Nguyen
2019-05-14 11:10       ` Philip Oakley
2019-05-18 12:17         ` Duy Nguyen
2019-05-19  0:09           ` Philip Oakley
2019-05-14 11:49     ` Antw: " Ulrich Windl
2019-05-15  7:34       ` Philip Oakley
2019-05-15  8:45         ` Ulrich Windl
2019-05-15 13:07           ` Philip Oakley
2019-05-15  1:50     ` Junio C Hamano
2019-05-15  7:13       ` Philip Oakley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0c9ec78a-9245-e1df-7ec6-a5d77d1a5261@iee.org \
    --to=philipoakley@iee.org \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).