Re: [Monotone-devel] restrictions and SVN type branches/tags?

[Derek Scherger]

Richard Levitte - VMS Whacker wrote:
> I'm not sure I followed.  Does that mean that you can select what
> particular files should be part of the change you're about to commit?
> I would actually enjoy such a possibility, as the way I hack around
> sometimes includes changes that really do not belong in the database.

that's right, you can limit which files are committed with the stuff in the 
net.venge.monotone.restrictions branch. this is still a work in progress that probably 
needs some cleaning up and will need updating when the context/revision stuff graydon is 
working on lands but it turned out to be a relatively simple change.

if this isn't available from graydon you can get it from my netsync server at 
www.echologic.com with the following public key.

[pubkey address@hidden
MIGdMA0GCSqGSIb3DQEBAQUAA4GLADCBhwKBgQDACq6E1Dm1CXq7czaZo4/ycKgqQShewclx
HAcweq0imG/NucgdDgsw/3ZIOq+IVwXya+Axqst3sHz5km8s94XvBcgjzHF1jyeGiN9UEBSN
R+ecT8rF5ogC6OsBpgTMHYASpcuGimLsupz1HE7bz/2o95hIdb6NaV4Ni2FYy/VoiwIBEQ==
[end]

> derek> Creating a branch is really nothing more than just putting a
> derek> new branch cert on some manifest.
>
> Hmm, isn't that a bit simplistic?  I'm not entirely sure how branching
> is supposed to work, but doesn't what you say mean that a specific
> manifest is changed to belong to the new branch, thus affecting
> everyone who happens to update from the same head as you do?  If that
> is so, I will probably see that as a bug.

adding a cert to a manifest doesn't change the manifest, the cert is just associated with 
the manifest. the manifest may belong to many different branches but it doesn't know that. 
the branches sort of reach out and grab the manifest through their certs.

--
Cheers,
Derek