Bug 3036 - Confusing message "abort" upon creation of a new queue when unapplied patches exist in the default queue
Summary: Confusing message "abort" upon creation of a new queue when unapplied patches...
Status: RESOLVED FIXED
Alias: None
Product: Mercurial
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: unspecified
Hardware: All All
: wish feature
Assignee: Bugzilla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 09:18 UTC by vasjaforutube
Modified: 2012-10-19 14:25 UTC (History)
3 users (show)

See Also:
Python Version: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vasjaforutube 2011-10-05 09:18 UTC 
If I create a new queue with 

& hg qq foo

while there are some unfinished patches in the default queue, it says,
abort: patches applied - cannot set new queue active

But in fact it does create a new queue, it just doesn't switch to it. I find
this message confusing - I expected that message "abort" corresponds to
abort of the whole transaction, not its part. :)
Comment 1 Bugzilla 2012-05-12 09:24 UTC 

--- Bug imported by bugzilla@serpentine.com 2012-05-12 09:24 EDT  ---

This bug was previously known as _bug_ 3036 at http://mercurial.selenic.com/bts/issue3036

Bug Status was UNCONFIRMED but everconfirmed was true
   Setting status to CONFIRMED
Comment 2 Bryan O'Sullivan 2012-10-05 13:10 UTC 
Fix in crew: http://hg.intevation.org/mercurial/crew/rev/4f2f0f367ef6