Messages in this thread |  | | | Date | Tue, 28 Jun 2005 16:45:12 -0400 (EDT) | | Subject | Re: Mercurial vs Updated git HOWTO for kernel hackers | | From | "Sean" <> |
| |
On Tue, June 28, 2005 4:27 pm, Kyle Moffett said: > On Jun 28, 2005, at 14:01:57, Matt Mackall wrote: >> Everything in Mercurial is an append-only log. A transaction journal >> records the original length of each log so that it can be restored on >> failure. > > Does this mean that (excepting the "undo" feature) one could set the > ext3 "append-only" attribute on the repository files to avoid losing > data due to user account compromise? >
Probably. In Git, which is a bit more flexible than Mecurial you can chmod your objects to read-only or use the ext3 immutable setting to protect your existing objects. You can even have a setup where objects are archived onto write-once media like DVD and still participate in a live repository, where new objects are written to hard disk, but older object are (automatically) sourced from the DVD.
Sean
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |