"Lars Hjemli" <lh@elementstorage.no> writes:

quoted text
> On 8/4/07, David Kastrup <dak@gnu.org> wrote:
>> Now I think that I basically have no chance figuring this out on my
>> own sufficiently well to be able to improve the documentation.
>
> Remote-tracking branch:
>   A local copy of a branch in another repository. This kind of branch
>   cannot be updated by 'git-commit' but only by 'git-fetch' (hence
>   indirectly by 'git-pull' and 'git-remote update'). If you try to
>   'git-checkout' a remote-tracking branch, you will get a detached HEAD.
>
> Local branch:
>   A branch to which you may commit changes. Optionally, the branch can be
>   configured to "follow" one of your remote-tracking branches. This means
>   that a 'git-pull' without arguments (when your local branch is checked
>   out), will automatically 'git-fetch' and then 'git-merge' the remote-
>   tracking branch.

Does that mean that specifying "--track" to git-checkout or git-branch
never creates a remote-tracking branch?

quoted text
> Example:
>
> Your local branch 'master' is setup to "follow"
> 'refs/remotes/origin/master'.

So --track/--no-track are actually supposed to be --follow and
--no-follow?

quoted text
> So if you do this:
>
> $ git checkout master
> $ git pull
>
> Then the 'git pull'-command will do this:
>
> $ git fetch -f origin master:remotes/origin/master

This is then tracking?

quoted text
> $ git merge remotes/origin/master

And this is then following?

quoted text
> The magic setup that makes this happen is the following lines in .git/config:
>
> [remote "origin"]
Namely: a remote-tracking branch "origin"

quoted text
>         url = git://git.kernel.org/pub/scm/git/git.git
>         fetch = +refs/heads/*:refs/remotes/origin/*
>
> [branch "master"]
>         remote = origin

Namely: follow the remote tracking branch origin?

quoted text
>         merge = refs/heads/master
>
>
> Was this helpful?

So we have remote tracking branches, and we have local branches
following remote tracking branches, and "--track" and "--no-track"
create local branches following or not following a remote tracking
branch?  And have nothing whatsoever to do with tracking or not
tracking a remove branch?

Talk about misleading option names here.

Then in man git-branch we have:

	In its second form, a new branch named <branchname> will be
	created. It will start out with a head equal to the one
	given as <start-point>. If no <start-point> is given, the
	branch will be created with a head equal to that of the
	currently checked out branch.

	When a local branch is started off a remote branch, git can
	setup the branch so that git-pull(1) will appropriately
	merge from that remote branch. If this behavior is desired,
	it is possible to make it the default using the global
	branch.autosetupmerge configuration flag. Otherwise, it can
	be chosen per-branch using the --track and --no-track
	options.

What does "remote branch" in this context mean?  A local branch
following a remote tracked branch?  A remote tracked branch (which by
definition can't be checked out as a branch, since that leads to a
detached head)?  What does "start off" mean in this context?  If I
can't check out a remote branch, I can't start off on it, can I?

Does "--track" mean that the new branch will copy any "remote" lines
which incidentally don't point to remote branches as their name would
suggest, but rather to remote tracking branches?  And we want to have
the relation to the remote tracking branch preserved, not to the
actual remote branch?

I don't get it.  Really.  No chance.  There are fine distinction lines
in the git terminology, it would appear, and those lines are freely
ignored in naming options and configuration parameters.  And the
manual pages themselves are not overly concerned about explaining
those distinctions either.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html