Jon Bright <[EMAIL PROTECTED]> writes: [...]
> I can think of a couple of cases where the information's file > based. Stuff like "has been reviewed for classified information", or > "has been reviewed for third-party source" when doing an open > release of a previously proprietary product. Say you're porting > your latest and greatest product to some new version of the > language/compiler/whatever that you're using, you could also do some > kind of "Java1.5ified" cert, letting you gradually work through your > source tree and use the version control to keep track of which files > you've done and which not. Yes, both of those cases would be best done by marking the blob of bytes, I guess. I wonder if they're important enough to try and revive per-file certs. _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
