Strategies for push/merge problem?

[Arne Babenhauserheide]

Am Dienstag 15 Juli 2008 00:50:42 schrieb Alpár Jüttner:
> Finally, the "frequent commit" policy is probably a legacy of the
> locking model revision systems. Using mercurial, you will typically find
> it much better to commit larger block of changes, and synchronizing your
> repository even less frequently, for example when you more-or-less
> completely finished implementing a new feature.

And what about people who like to commit often, because (for example) they 
work on laptop and desktop and use Mercurial to synchronize the data? 

Or they use it to keep the state of where they were? 

It shouldn't ask people to change their ways, because it can adapt. 

And frequent commits keep my workspace clean, so I can always pull in the 
changes from others. 

Or did you rather mean "frequent pushes"? 

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/f81a432f/attachment.pgp