Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:
>> This is useful when you check out new changes with gitk.
>> Just copy/paste the old ref into gitk from the terminal.
>
> Why does "gitk ORIG_HEAD..HEAD" not work? (It also does the correct thing
> when pulling...)
For most projects and repositories with single interesting head,
that would work just fine.
If you use additional Pull: lines to track more than one remote
refs, this patch would help.
For example, if you are tracking my "next" while keeping an eye
on my "master" and "pu", your .git/remotes/origin file may have
something like this:
URL: git://git.kernel.org/pub/scm/git/git.git
Pull: next:origin
Pull: master:ko-master
Pull: pu:ko-pu
When "git pull origin" pulls my next branch into your current
branch (typically "master"), it also fast forwards your tracking
branches ko-master and ko-pu. If you want to see what I merged
in the meantime, you would want to get the old value of
ko-master and the new value and feed them to gitk (or git log).
ORIG_HEAD in this case was the old value of _your_ current
branch head, and is not useful to see what happened to my master
branch.
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html