best way to manage local code changes which shouldn't be propagated

[Arne Babenhauserheide]

Am Donnerstag 15 Januar 2009 22:02:57 schrieb Georg-W. Koltermann:
> thank you very much for your fast and detailed response, but using two
> repos and two branches isn't a real simplification over my previous way
> with mq.

The main advantage is that it avoids using any possibly history altering 
commands. You can't shoot yourself in the foot as easily as with MQ :) 

> The one important fact (maybe I didn't make it clear enough) is that I
> need those local changes during my development and test cycle, when I
> develop public work.

Maybe I also didn't read closely enough. 

How about a precommit hook which automatically does qpop -af and a commit hook 
which does qpush -a. 

I didn't test this, so be careful... and please tell us if and how it works! 

Best wishes, 
Arne
-- 
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software.
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20090115/d255b544/attachment.pgp