Re: [PATCH 09/10] user-manual.txt: explain better the remote(-tracking) branch terms

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Oct 27, 2010, 00:01 UTC
Message-ID: <vpqocag33mn.fsf@bauges.imag.fr>
In-Reply-To: <AANLkTinJQMSbW-bsEOS9610GXR7EtbESK_tLAfxt2ibK@mail.gmail.com>

Jay Soffian <jaysoffian@gmail.com> writes:

Show 11 quoted lines

> On Mon, Oct 25, 2010 at 2:08 AM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
>> +In this case, "origin" is called a remote repository, or "remote" for
>> +short. The branches of this repository are called "remote branches"
>> +from our point of view, and Git will keep a copy of these
>> +branches, called "remote-tracking branches" in the local repository.
>> +These remote-tracking branches are references that will be updated by
>> +"git fetch" (hence by "git pull"). See
>> +<<Updating-a-repository-With-git-fetch>> for details.
>
> "...and Git will initially clone these branches into so-called
> "remote-tracking branches" in the local repository.

I don't thinks it's a good idea to use the word "clone" here. "clone" is used for repository cloning, and I find it confusing to overload the word for branches.

> Thereafter, the
> remote-tracking branches are updated upon fetching from[1] or pushing
> to the remote. ([1] which also includes pulling.)

I don't like the [1] kind of footnote within the text, but I forgot to mention that "git push" updates the remote-tracking in my text. That'll be fixed in next version.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/