Concatenating changesets

Peter Arrenbrecht peter.arrenbrecht at gmail.com
Mon Dec 17 00:59:59 CST 2007


On Dec 17, 2007 5:11 AM, Barry Roberts <blr at robertsr.us> wrote:
>
> On Sat, 2007-12-15 at 10:07 -0600, Matt Mackall wrote:
>
> > A changeset should be a single well-defined change.
>
> Which is exactly why I want to combine them.  I frequently commit just
> because I'm going home (or out of town) and I want to be able to clone
> or pull my absolute latest.  Even if it doesn't build.  When the feature
> or fix is ready to share, those commits are worse than useless.
>
> But it sounds like people use mq instead of committing at times like
> this.  Right?

Yes. Gives you the added benefits of being able to
* insert new changes before others you're working on,
* update existing changes,
* split exisiting changes (with a bit of work), and
* version the evolution of a set of changes (a patch queue).


More information about the Mercurial mailing list