Strategies for push/merge problem?

[Arne Babenhauserheide]

Am Dienstag 15 Juli 2008 04:45:41 schrieb Douglas Philips:
> 	"main" repo > local clean copy -> <n> working clones.
>
> Flow is that when I want to get "main" changes, I pull to local clean
> copy, then pull again into whatever working clones I care about.
> Changes get pushed form the working clones to the pushee tree, never
> to local clean copy. Local clean copy exists so that I can <snap
> fingers>clone</snap fingers> to get a fresh tree to do a one-off, or
> whatever.

Problem: "hg push" doesn't push to the pushes tree automatically. 

A clean copy with an incoming hook (push on incoming) could solve this. 

Maybe a "exact" option (or similar) which copies over the default and 
default-push paths would help here, but it might become a security problem 
(for example if I use Username and Password in my push path). 

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

-- 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/20080715/6e0fa3c1/attachment.pgp