Re: [Monotone-devel] Re: Rosterify and certificate keys

[Nathaniel Smith]

On Tue, Apr 11, 2006 at 02:24:05PM +0100, Bruce Stephens wrote:
> So I think producing the map from old revision hash to new revision
> hash is doable.  And it seems obvious that it would be easy enough to
> then produce per-key scripts to create suitable replacement certs, and
> similarly, that it would be easy (well, probably) to remove the ones
> created by the rosterify process.
> 
> 
> When I do our database, I think I'll hack mtn to do it, though.
> 
> I imagine mtn knows this mapping while it's converting the database,
> so I'd guess it would be straightforward to change it to dump it.
> 
> While it's at it, it can dump the revision cert hashes that it's
> creating (or directly a script to remove them), and per-key scripts
> for creating replacement certs that I can give colleagues.  
> 
> Does that make sense?
> 
> I guess it's too late for people who have already converted, but would
> such a patch be of value to enough people that I should try and write
> it cleanly enough that it could be included in the mainline?

A fair number of people are holding off until 0.27ish to upgrade, so
it'd probably be valuable.  I'd certainly accept patches to do things
like output a mapping between old and new ids (to do... whatever it is
you wanted to do with it, I guess?), or replacing rids in certs with
the new name.  (Rule: 40 chars hex that match an old rid can be
pretty safely replaced with the corresponding new rid; all other
strings left untouched.  This replacement function requires good
tests, because conversion is an easy time to corrupt data!)

Cheers,
-- Nathaniel

-- 
"...these, like all words, have single, decontextualized meanings: everyone
knows what each of these words means, everyone knows what constitutes an
instance of each of their referents.  Language is fixed.  Meaning is
certain.  Santa Claus comes down the chimney at midnight on December 24."
  -- The Language War, Robin Lakoff