Re: [Monotone-devel] movable monotone tags

[Stanislav Karchebny]

On Saturday 28 May 2005 06:04, Nathaniel Smith wrote:

> AFAICT it's perfectly _possible_ to support versioned tags; you can
> think of each tag as being like a unique file, and its contents the
> revid that's being tagged -- then it's clear that if you know how to
> version files, you can come up with a way to version tags as well.

This is what I proposed in the first email, actually:

> > 2) Proposal: version tags similar to how we version the files themselves.
> > So a tag on revision X can be moved to revision Y specifying that its 
ancestor 
> > revision was X. Then different tag moves in different trees can be tracked 
> > and resolved using pretty much the same merge conflicts resolution.
> > 

> Practically speaking, though, it's a big pain to add another "type" of
> object that can be versioned, teach all the code about it, teach
> netsync about it, and so on and so on.  So I wouldn't expect to see
> this in monotone particularly soon...

I understand that.

> It does suggest another possibility for dealing with the original use
> case, where tags are used to tell an autobuilder what to build: you
> could instead have a branch that contains a file telling the
> autobuilder what to build, and the autobuilder checks out this file,
> looks at it, and does whatever.  Dunno if this is better or worse
> than the other solutions suggested, but it's an option :-).

Sounds doable. This is what we do for another library in cvs actually =)

-- 
Best regards,
Stanislav Karchebny

Skype name: berkus
Get skype for free from www.skype.com

pgphC_h9SOq3s.pgp
Description: PGP signature