[Bug 4956] New: In the event of a local conflict with hg qpush, tell the user what files are locally conflicting

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Tue Nov 17 23:55:59 UTC 2015


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

            Bug ID: 4956
           Summary: In the event of a local conflict with hg qpush, tell
                    the user what files are locally conflicting
           Product: Mercurial
           Version: 3.6
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: mq
          Assignee: bugzilla at selenic.com
          Reporter: faheem at faheem.info
                CC: mercurial-devel at selenic.com

This is a followup to https://bz.mercurial-scm.org/show_bug.cgi?id=4604, which
is about `hg qpush` silently failing if there are conflicts / local changes.

While #4604 has been fixed, it would be nice if the new error message 

    abort: conflicting local changes found
    (did you forget to qrefresh?)

said *what* local changes were found, rather than leaving the user to guess
what they were. And, assuming they are multiple such conflicts, maybe just
report the first one?

Regards, Faheem

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


More information about the Mercurial-devel mailing list