Strategies for push/merge problem?

Greg Lindahl lindahl at pbm.com
Wed Jul 23 17:19:27 CDT 2008


On Wed, Jul 23, 2008 at 08:00:20PM +0000, Risto Kankkunen wrote:
> > > However, I'm wondering couldn't you use branches in Mercurial for the same
> > > thing: develop, commit and push your changes to a separate branch until they
> > > are stable enough and pass the test suite before merging into the mainline.
> > 
> > Isn't it simpler to use a separate repo until the tests pass? Which is what
> > people are already doing when they don't push until the feature is done.
> 
> The situation I'm referring to is when people want to record for posterity the
> steps they took to implement a feature instead of the zeus athena alternative.

I was suggesting pushing all the history when you do push. So it's all
there.

The "finding the repo" problem exists before the push, though.

Separate repos solve some of the problems that branches do in CVS. So
branches have a smaller use case in Mercurial.

-- greg



More information about the Mercurial mailing list