avoiding cluttered history?

[Ed Keith]

Sometime I find myself working on problems where the solution is not obvious and I explore lots of dead ends before hitting on the solution. Back in the dark ages I frequently archived my work and only checked the final results into version control. Now rather than archiving, I create a temporary hg repository that I work in then I check the final results into my main repository and publish it. 

In the past the official repository has been svn, and I have been quite satisfied with this work flow, but I will soon be working on a project which is officially using hg. There is no reason why this would not continue to work, but somehow it feels suboptimal. It looks like MQ might be better, but I though I'd ask the list before diving into it because it looks like a steep learning curve.

    -EdK

Ed Keith
e_d_k at yahoo.com

Blog: edkeith.blogspot.com