From: Philip Oakley <philipoakley@iee.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Missing branches after clone
Date: Wed, 15 May 2019 08:13:19 +0100 [thread overview]
Message-ID: <a05fb45a-69d7-a12b-e76c-f11e985f4a65@iee.org> (raw)
In-Reply-To: <xmqq5zqc8ozn.fsf@gitster-ct.c.googlers.com>
On 15/05/2019 02:50, Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.org> writes:
>
>> 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.
> Yup, I thought we long time ago decided to discourage use of "remote
> branch(es)" in our documentation to help unconfuse users and stick
> to the term "a remote-tracking branch" (the "remote-tracking" is a
> hyphenated one word)?
I believe we are consistent in using the 'rtb' phrase (I've not checked
the hyphen), but for those uninitiated in the duplicitous ways of
distributed versioning systems, they can still think that the phrase is
simply saying that local branch A will be updated to the state of remote
branch B when do a fetch from that remote.
I.e. they think tracking is a direct linkage via fetch, rather than an
indirect linkage via a local rtb (a concept that has not yet entered
their head, and if if they are aware of the possibility, they haven't
joined the dots). Hence my spelling it out the 'French' way.
>> 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'.
> Yup. FWIW, when I need to refer to the last one, I'd always say "a
> branch at the remote" to avoid the confusing term "remote branch".
>
yes, it's tricky. I've shot my foot off a number of times.
Thanks
Philip
prev parent reply other threads:[~2019-05-15 7:13 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
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 [this message]
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=a05fb45a-69d7-a12b-e76c-f11e985f4a65@iee.org \
--to=philipoakley@iee.org \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).