Re: [bug] git checkout lies about number of ahead commits when switching from detached HEAD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Mar 19, 2011 at 10:53:13PM +0100, Piotr Krukowiecki wrote:

> It says "by 0 commits" when going back from detached HEAD to
> master branch:
> 
> 
> $ git checkout HEAD^
> 
> $ git checkout master
> Previous HEAD position was af4c62a... Merge branch 'maint'
> Switched to branch 'master'
> Your branch is ahead of 'origin/master' by 0 commits.
>                                         ^^^^^^^^^^^^
> 
> $ git status
> # On branch master
> # Your branch is ahead of 'origin/master' by 1 commit.
>                                           ^^^^^^^^^^^

Hmm. My guess is that the new "check for connectivity when leaving
detached HEAD" test is polluting the commit flags for the ahead/behind
test.

[bisect bisect bisect]

Yep, it bisects to 8e2dc6a (commit: give final warning when reattaching
HEAD to leave commits behind, 2011-02-18). We probably need to clean the
uninteresting flags between the two traversals.

-Peff
--
To unsubscribe from this list: 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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]