Best Practices: Keeping the Repository History Understandable

[Mark A. Flacy]

On 2007.07.22 19:04, Gregory Collins wrote:
> On Sun, Jul 22, 2007 at 02:25:47PM -0500, Mark A. Flacy wrote:
> > On 2007.07.22 11:44, Evan Jones wrote:
> >
> > Why not this?
> >>  
> http://www.selenic.com/mercurial/wiki/index.cgi/TipsAndTricks#head-5b2e4d05ef883f9b5724f8f1e6d56487545159d3
> 
> Because you'd have to use e.g. the transplant extension if you wanted
> to rebase your local branch against upstream changes. Does that
> solution work as well as MQ?

*Shrugs*  It depends upon the problem space.  From the OP narrative, it  
seemed as if they were using hg for their own projects and wanted to  
wrap up working change sets into a single logical commit to the shared  
branch.  MQ seems like an odd tool to use for that purpose, but that may  
just be my unlearned opinion. (I haven't used MQ that much, so I am not  
being sarcastic.)

-- 
Mark A. Flacy