Best Practices: Keeping the Repository History Understandable
Gregory Collins
greg at maptuit.com
Sun Jul 22 17:43:53 UTC 2007
On Sun, Jul 22, 2007 at 12:44:21PM -0400, Evan Jones wrote:
> Maybe the answer is use MQ to avoid committing changes which aren't
> 100% polished and ready to go into the main repository? Or maybe
> this is a non-issue. In browsing the Mercurial or Mozilla project
> histories, I don't see a lot of "temporary" commits, so I'm assuming
> that people aren't doing the above. So what are people doing?
That's what I do. MQ makes this problem (mostly) go away, although
things go "wrong" a little more than I'd like (I've become an expert
"recountdiff" user). I also wish that three-way merge was less
painful; the qsave/pull/update/qpush -m/qpop X 2/rm -rf cycle is
pretty hairy.
Gregory Collins <greg at maptuit.com>
More information about the Mercurial
mailing list