-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian May wrote: > I can think of two evil reasons: > > * somebody committed data without permission and copyright owner is > jumping up and down threatening legal action if it isn't removed > immediately.
AFAIK, this is the case they're concerned with. > So I suspect removing the trail my be required, but this is going to > be evil, and potentially break past revisions - it might just about be > better to start a new archive from scratch. > > Also, what happens if only one line of one file is under dispute? Or > if the dispute is resolved and the copyright owner agrees the code can > stay after it has already been obliterated? I guess the two main approaches may be: "forbid a revision" or "forbid a specific (file) version". The first has the problem that it "breaks" the chain on hashes from the root of the tree up to the current latest revision, but has no problems in having the same content later on, if agreed upon. The second forbids a file content altogether, which is kinda sensible (is that very content which is not yours, not the fact that it is in revision xyz together with other thousand files) and could let every revision logic work as expected, except checkout and update would extract the full revision "except file XYZ, because its content is forbidden". If the content is to be had AGAIN... (but I'd consider this even more rare than having to forbit it in the first place!) I guess either: a. it is a source file: changing a single char in the file (e.h.: whitespace) can solve the problem b. it is a binary file that must be exactly so: I guess an epoch is to be used as last resource... - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP & X.509) www.lapo.it (Jabber, ICQ, MSN) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFWr7AAAoJELBiMTth2oCDzxoP/03pN3JsBKIadEgnKMQwuCmR aC2RM9s6B4zexq+s4BXRNIW0Ioravvx8Vq90vOefaUSuVNDVWPt01TwdyErp5ma2 kks0oLQWpi64K05Njfw64CE6Apcxpzvj8RpnErGEqmpeQabsJV3ZQ7U+63yPpFeq SfNpjxwxcG4d6kX2OPMOy6JMVLbU7WOyA1EeblEfcGNzM4smXag7FM5qPz6Dn0qO YOeYEptU8hYMgx/dM+ktzZ41vhOjktd2GMIi/EeTINRAxICe7dV/sisvONvltdG9 8qnyi/0hRvcB/l1ZcAA8o4bktrp+BGaaosRO9O19DKaUbgL++P720i4InbWNmXrc w9IkMnEIinL7utDIZIlektseFETGxWa7CMjDTOk0tprZLLeI4zRkoicE2m9ymMz/ B+cBgCwuppteEhsQ5feUN2UuFGyUSMFYX8wL5jO9Pw9VM9j8WZcW2eTw9D31NCMf eCpyf+YSaFBPlP6LPnWQxfOazpgqD2zEuFwwRSBz6bdO9LZWv3PT85p8RebzaawZ mj242cVEDcFlrgZvLVls64tjJq5e/ABg2yKdj/C0F804Bs4UUO/cdzD4KcdauTmc ocgIqIatGYBc259xzW/Xfukj+t4KvOyPY2iHNZQTSE1HIgb8gt+pGnZZpYBs9jyR LKZj1iRMgiG/eV16WkIS =Nj8c -----END PGP SIGNATURE----- _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel