"Stripping" changesets from the past of a repository

[Jim Hewes]

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.

Jim


-----Original Message-----
From: mercurial-bounces at selenic.com [mailto:mercurial-bounces at selenic.com]
On Behalf Of Igor Lautar
Sent: Monday, November 16, 2009 6:43 AM
To: Fabrizio Giudici
Cc: mercurial at selenic.com
Subject: Re: "Stripping" changesets from the past of a repository

Hi,

On Mon, Nov 16, 2009 at 1:25 PM, Fabrizio Giudici
<fabrizio.giudici at tidalwave.it> wrote:
>
> 1. Either by stripping a specific set of resources from a given revision
> **backwards**
> 2. Or eventually scratching all revisions before a given one "R", so that
it
> seems that the repository has been created at revision "R".

You can something like that using hg convert. Specify from which
revision (your 'R') to start convert into a new repo. Note that you
change changeset IDs, but I think its not possible to do what you want
w/o actually changing IDs.

Regards,
Igor
_______________________________________________
Mercurial mailing list
Mercurial at selenic.com
http://selenic.com/mailman/listinfo/mercurial