Re: [Monotone-devel] Re: comments on net.venge.monotone.workspace-merge.migration

[Daniel Carosone]

On Thu, Aug 24, 2006 at 10:05:08PM -0600, Derek Scherger wrote:
> Marcel van der Boom wrote:
> >This currently allows me to quickly put a number of revisions in the 
> >_MTN/revision file and get a feel where the workspace is at and what 
> >needs to be done to upgrade/downgrade it to some revision we want. 
> 
> This was exactly the thing I was looking for when I first stumbled on 
> monotone a few years ago and was the initial point of my associated 
> nvm.noclobber branch. One possible alternative might be something like 
> 'mtn checkout/update --nofiles'.
> 
> Basically, "attach" this "detached" directory tree to monotone so I can 
> see what sort of state its in. 

My use for writing to _MTN/revision was similar: when migrating
pre-0.26 workspaces to 0.26, I needed to replace the pre-roster revid
with the post-roster revid (as well as rename the dir, of course).  In
a few cases, I had to stumble around the graph a little and guess the
best new-rev to match the base for uncommitted local changes.

--
Dan.

pgpvfbVWKqk1W.pgp
Description: PGP signature