Bug 2218 - Importing an existing changeset is "bad"
Summary: Importing an existing changeset is "bad"
Status: RESOLVED FIXED
Alias: None
Product: Mercurial
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: unspecified
Hardware: All All
: normal bug
Assignee: Bugzilla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 11:05 UTC by Steve Borho
Modified: 2012-05-13 04:51 UTC (History)
2 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 Steve Borho 2010-05-27 11:05 UTC 
$ hg clone "any repo" test
$ cd test
$ hg up -r -4
$ hg export -r -3 > foo
$ hg qimport foo
$ hg qpush
$ hg qpop
abort: popping would remove a revision not managed by this patch queue

My guess is qpush should bail and not update the status file if it doesn't
create a new changeset.  The normal import command should also note this
condition and report it.
Comment 1 Steve Borho 2010-05-27 11:07 UTC 
Perhaps it's easier to check if qpush creates a head changeset?
Comment 2 HG Bot 2012-02-01 14:00 UTC 
Fixed by http://selenic.com/repo/hg/rev/74d00b5d00cc
Matt Mackall <mpm@selenic.com>
qpush: avoid trying to manage existing history (issue2218)

(please test the fix)
Comment 3 Bugzilla 2012-05-12 09:09 UTC 
--- Bug imported by bugzilla@serpentine.com 2012-05-12 09:09 EDT  ---

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