Skip to content
Snippets Groups Projects
Select Git revision
0 results

hg

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Matt Harbison authored
    I've hit this a couple of times, where pulling with a dirty `wdir` obsoletes
    `p1` and updating to the successor results in merge conflicts.  The problem was
    resolving them failed immediately, complaining that the old checkout was
    filtered.
    
    The change in `test-rebase-obsolete.t` is because there's an outstanding merge
    conflict in a rebase operation.  The summary prompt to merge seems incorrect for
    this scenario, but that's an existing issue.
    
    Differential Revision: https://phab.mercurial-scm.org/D8980
    aaeccdb6
    History
    Name Last commit Last update