[Bug 5366] New: Phantom commits reported by `hg in` that can't be pulled

bugzilla at mercurial-scm.org bugzilla at mercurial-scm.org
Mon Sep 12 11:52:18 EDT 2016


https://bz.mercurial-scm.org/show_bug.cgi?id=5366

            Bug ID: 5366
           Summary: Phantom commits reported by `hg in` that can't be
                    pulled
           Product: Mercurial
           Version: 3.9.1
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: evolution
          Assignee: bugzilla at selenic.com
          Reporter: russ at perspexis.com
                CC: mercurial-devel at selenic.com,
                    pierre-yves.david at ens-lyon.org

I am running hg 3.9.1 and evolve 5.4.1.

I have a repo where `hg in` reports two incoming changesets, but `hg pull` sees
nothing.  They do not appear to be hidden changesets.  There *are* changesets
with the same commit messages, but they aren't the same changesets.

Here's a summary of the situation:

```
$ hg pull
pulling from <snip>
searching for changes
no changes found
$ hg in
comparing with <snip>
searching for changes
changeset:   312:21a2dfe8857b
user:        russ
date:        Wed Jul 27 16:45:36 2016 -0400
summary:     update requirements.txt and added top_level_requirements.txt

changeset:   321:f002fa11364c
user:        russ
date:        Fri Sep 09 14:39:24 2016 -0400
summary:     russfixes on error capture issues

$ hg log --hidden | grep "update requirements.txt" -A 0 -B 3
changeset:   320:38f951d76508
user:        russ
date:        Wed Jul 27 16:45:36 2016 -0400
summary:     update requirements.txt and added top_level_requirements.txt
$ hg log --hidden | grep "russfixes on error" -A 0 -B 3
changeset:   325:86a8a1d53052
user:        russ
date:        Fri Sep 09 14:39:24 2016 -0400
summary:     russfixes on error capture issues
```

Note that the changesets reported by `hg in` don't match the ones found by `hg
log`.  Also note that the --hidden is not needed to find the matching commit
messages.

This problem existed in this repo with earlier mercurial and evolve versions
(hg 3.8 and evolve version at "@-as-of-3 months-ago") as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list