Migrating from CVS -- avoiding multiple heads.

Matt Mackall mpm at selenic.com
Tue Aug 2 02:34:45 CDT 2005


On Sat, Jul 30, 2005 at 01:20:18PM -0400, Michal Ostrowski wrote:
> I would like to try to replace CVS with mercurial for a fairly large
> software project.  In our development model we have a single CVS
> repository which multiple people commit to and I would like to retain
> that development model.   Unfortunately I have not found a way in
> mercurial to ensure that two "pushes" by distinct developers don't cause
> problems.  
> 
> Is it feasible to have an option to push/pull which will cause the
> operation to fail if the destination contains changesets not in the
> source?   

Added in tip. You're not the first to ask.

> If is feasible to make this an attribute of the repository
> rather than depending on the command line arguments? (This way I don't
> depend on the pusher to remember to use the command-line flag.)

It's the default now. A friendly hint is given when it fails,
reminding you to sync or merge, and to use -f if you really meant to
add a new head.

-- 
Mathematics is the supreme nostalgia of our time.


More information about the Mercurial mailing list