Alexey Muranov <alexey.mura...@gmail.com> writes:
> On 20 Jul 2012, at 09:11, Johannes Sixt wrote:
>> Note the difference between "tracking branch" and "remote tracking
>> branch"! The "remote tracking branches" are the refs in the refs/remotes/
>> hierarchy. The "tracking branches" are your own local branches that you
>> have created with 'git branch topic thatremote/topic' (or perhaps 'git
>> checkout -b'). The paragraph talks about the latter.
> Hannes, thanks for the explanation, so i was confused once again.
> Various blog posts do not make the terminology clear, for example
> sais that there are only "two types of branches: local, and
> I think i was also misguided by Konstantin, who wrote that "you
> create a remote tracking branch when you intend to actually
> *develop* something on that branch" :).
I was re-reading the backlog today, and saw this topic fizzled out.
We obviously cannot fix third-party documentation that teach lies to
people, but is there something we can do to improve our own
documentation with respect to this confusion?
As I wrote it elsewhere, I try to avoid the bareword "tracking" in
general, and call the local branch you build on something like "your
'next' branch that forked from origin/next remote tracking branch"
myself. Perhaps we can start from checking the documentation with
such a phrasing discipline?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html