"Stripping" changesets from the past of a repository

[Fabrizio Giudici]

Jim Hewes wrote:
> I thought I had read that changeset IDs were calculated based on content
> from earlier revisions. If so, wouldn't it be possible when stripping out
> earlier revisions to base the new repository on an initial dummy revision
> that had a dummy changeset ID that caused all subsequent changesets IDs to
> be the same as they were before?
>
> The reason I ask about this is because I was thinking about having a build
> process which notes all the changeset IDs of each project when building a
> release. Then we don't have to always remember to add tags to revisions. The
> changeset IDs can act as tag. But then you could never strip off old
> revisions without messing that up.
>   
I've used hg changeset ids embedded in binary artifacts, and used them 
to mark builds in the continuous integration. But I've switched to hg in 
July and in the meantime all the relevant projects are undergoing other 
engineering changes, so there haven't been official releases - that's 
why I can live with changing all the ids. In any case, I'm keeping an 
archival copy of the original repos.

-- 
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici at tidalwave.it