abort: queue top not at same revision as working directory
Dustin Sallings
dustin at spy.net
Tue Oct 9 16:56:51 CDT 2007
On Oct 9, 2007, at 13:36 , Marcin Kasperski wrote:
> PS I still feel that hg clone, hg push and hg pull should either do
> the Right Thing, or croak ("Can't push as the remote repository has
> patches applied, qpop -a that repo before trying again" etc). What
> is the Right Thing? Well, sync-ing BOTH .hg and .hg/patches/.hg
> for sure, the requirement to qpop on the receiving side
> should probably stay (I can't imagine otherwise), but the sending
> side context should not matter....
Note that pull and update are different concepts. I might want to
pull in some new code, but not change my working tree just yet. It's
really update that you're worried about in your mq tree. You also
want to consider anything that might push or pull an mq changeset
accidentally.
--
Dustin Sallings
More information about the Mercurial
mailing list