Concatenating changesets

[Dustin Sallings]

On Dec 14, 2007, at 10:38, blr at robertsr.us wrote:

> I really like the idea of logically mapping changesets to defect
> fixes or features.  But I also like to commit early and often in
> my own working repository.  I've tried the "Concatenating
> multiple changeset into one changeset" from the Tips and
> Tricks (http://www.selenic.com/mercurial/wiki/index.cgi/ 
> TipsAndTricks),
> but it has a couple of problems.
>
> Most importantly, the final clone takes just over a minute with
> my code base.  That makes our old CVS faster in most cases.

	It sounds like mq might be the right tool for you for one of two uses:

	1)  You can use it directly where you ``qrefresh'' instead of commit  
(maybe a qci, too).
	2)  You can use it to perform the above by doing a ``qimport'' of all  
of the changesets (you can do it in a range) and then using ``qfold''  
to combine all the changesets.

> Is combining changesets a bad idea (amd I still thinking in CVS),
> or are there other, faster ways to do this with hg?


	It's up to the user.  I think it's a bad idea, some people think it's  
a great idea.  You seem to be leaning more to the right side of that  
sentence.  I wouldn't say it's a CVSism.  I've always committed early  
and often regardless of my tools.

-- 
Dustin Sallings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20071214/8b88f0cb/attachment.htm