-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruce Stephens wrote: > I'm not sure how you'd get rid of a file. I guess you have to take > the revision that added it, commit another one that doesn't add it, > then rebase all its descendents?
What about adding a "forbidden_content (id, reason, certificate)" table to the DB and: a. delete the files with version "id" from the file table b. delete the delta which "produces" that version from the delta table c. adjust the delta of the following version to skip the deleted one d. spread this table like every other This would of course add an invariant to be kept valid: the version listed as "forbidden_content" must be deleted (and deltas adjusted) from the DB. In case the users extract the revision with contains file version "id" the file would not be found (of course), but the usual "hey, I've lost something, PANIC!" message should become a warning more like "the file 'id' was not created because its content was forbidden". I guess this would be as far as a distributed system can get regarding the obliterate feature (or the "punch holes" features as someone describes it). Does that sounds like a sound solution? (yes, it was a joke) As FreeBSD seems to consider it a very valuable feature (and it's obvious to everyone that it is my dream-in-a-pocket that monotone could be selected as the successor of CVS+Perfoce by them, though it is quite improbable), it could be my first serious code contribution... - -- 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 iQIcBAEBAgAGBQJFVlDfAAoJELBiMTth2oCDzcgP/iv0Sl1GG8+/t7u7ZqI0GRPp fL3ZLywGcIcArLCZblmqYZLDnMCik1T66SJPzBhy9ULWnM3mrjIKDh3XzlkQhC95 tdLmXmw1MjteEEoAwWncntgXnZP7uPiqGWISZJbrPytCuWOdyuryLsFbEKZ2zIld OgFnObaX/qFhPH8jbHoQz4P2pGeC9ptHiGd/xkoOqVjXv0IyuVQPcTXOf/nN73/j dyvhvxB8HJzkJJVwzOaNMJAAfu+INgoB2lPLfXVLzcWtEaLHjJjRX2ct15hr1n4w 4qyK9DwS4zzrIDr5v+52rOXSBWFGYD5xrLtEeWsuTknuv+b4TJWtbswaJA0/wnNt eIjow1+SVfx32+5qGbGx0bsJhZhG/POSpikeBIijQ0sh4mSQT5IILaWZdccCNH07 dpL2Hk5HRdOvwVYno9PmUYvBBZbZU7zNrIdhpNWxUQM90cM63RKLjl0oAwBhAY2p n19FqWBr7maCo03P75FjBFHDSDkaUfPeiIyUmii+FEtrtOPx05kVr/aVvFsT3IYU XWrhJt+joVvo7DYyyDUrZNXmaCHMk3NKSaWiHVjE3kuSShcxoewOOfymTIsX2c2O wgOyzFtAqee0ir/xY++eTcSaUCjP8zvj8cHDjenCRZCL5WDNY1oYeiz8G1OuA8cW e9EZgM8GKWhc3wT8Uakt =bPXR -----END PGP SIGNATURE----- _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel