[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mercurial-devel
Subject:    [issue844] mqmerge sequence blows up if saved queue is popped first
From:       Patrick_Mézard <mercurial-bugs () selenic ! com>
Date:       2007-11-24 21:19:18
Message-ID: 1195939158.76.0.903356366378.issue844 () selenic ! com
[Download RAW message or body]


New submission from Patrick Mézard <pmezard@gmail.com>:

I think it is related to issue 764, if the current queue is popped first then
strip is called afterwards and everything is fine.

MqMerge wiki entry ends the sequence by popping the current queue then the saved
one, but the hg book says the saved queue can be popped and deleted afterward,
not talking about the current queue. Maybe we should add a temporary warning in
the book.


#!/bin/sh

echo "[extensions]" >> $HGRCPATH
echo "hgext.mq=" >> $HGRCPATH

hg init t2
cd t2
echo a > a
hg ci -Am init
echo b >> a
hg qnew -f changea
hg qsave -c -e
hg up -C 0
HGMERGE=true hg qpush -m -a
hg manifest
# Pop the saved queue first.
# It works fine if the current queue is popped first
echo % pop the saved queue
hg qpop -a -n patches.1
echo % pop the current queue
hg --traceback qpop -a
echo % pushing back
hg qpush -a
hg verify

----------
messages: 4362
nosy: pmezard
priority: urgent
status: unread
title: mqmerge sequence blows up if saved queue is popped first
topic: mq

____________________________________________________
Mercurial issue tracker <mercurial-bugs@selenic.com>
<http://www.selenic.com/mercurial/bts/issue844>
____________________________________________________

_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@selenic.com
http://selenic.com/mailman/listinfo/mercurial-devel

[prev in list] [next in list] [prev in thread] [next in thread]