Strategies for push/merge problem?

Arne Babenhauserheide arne_bab at web.de
Wed Jul 16 01:24:25 CDT 2008


Am Dienstag 15 Juli 2008 15:55:01 schrieb Douglas Philips:
> > A clean copy with an incoming hook (push on incoming) could solve
> > this.
>
> if the hook's push never fail.. and doesn't need credentials and ...

You can add credentials to the hook, but then they'll lay around in your hgrc 
as plain text. 

Wish: encrypted passwords in hgrc (somehow). 

> I think there are already some discussions about having some of
> the .hgrc entries participate in a clone... but I don't recall any
> recent discussions and wasn't following it closely.

Good to know, thanks! 

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/20080716/39c5d5f3/attachment.pgp 


More information about the Mercurial mailing list