Concatenating changesets
Giorgos Keramidas
keramida at ceid.upatras.gr
Mon Dec 17 03:48:23 CST 2007
On 2007-12-16 21:11, 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? I'm starting to play with mq now to see how it works.
When merges are not involved, I use MQ to handle a stack of local
patches.
Having a local stack of patches on a repository with `linear' history
allows me to take advantage of tools like `webrev' from the OpenSolaris
team too, to generate nicely formatted HTML pages which can be uploaded
on a web page for online reviews of work-in-progress too. That has
turned out to be a pretty cool of getting a review from people who don't
have Mercurial or don't use it for their own work :)
More information about the Mercurial
mailing list