From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] venti woes with brand new install
Date: Sun, 9 Sep 2007 15:22:14 +0200 [thread overview]
Message-ID: <5d375e920709090622k2441b98fsf6be8a04282e139d@mail.gmail.com> (raw)
In-Reply-To: <b535a947a81ada98beae469c091f722f@quanstro.net>
> history is not revision control.
One doesn't need to use revision control to keep a reasonable
changelog, see for example the /CHANGES file in both Inferno and p9p
(obviously revision control can be used to maintain a changelog,
whatever that is a good or a bad idea is a matter of argument).
> it works at the filesystem level as a complete
> copy of each file is available for each day in the "dump" file
> system. thus it works on any file witha granularity of 1 day.
> many changes to a file during a day show up as a single
> change from day n to day n+1.
Actually, fossil works with much more fine grained granularity than
one day, it is up to the user to decide how that granularity should be
and for how long such snaps should be kept. (sorry for nit picking,
you probably knew that already, just was pointing this out for whoever
might not know)
uriel
next prev parent reply other threads:[~2007-09-09 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 12:09 John Soros
2007-09-08 13:43 ` erik quanstrom
2007-09-08 14:27 ` gabidiaz
2007-09-09 12:01 ` John Soros
2007-09-09 12:05 ` erik quanstrom
2007-09-09 12:57 ` John Soros
2007-09-09 13:08 ` Uriel
2007-09-09 13:13 ` erik quanstrom
2007-09-09 13:22 ` Uriel [this message]
2007-09-10 8:12 ` SHRIZZA
2007-09-10 8:39 ` Uriel
2007-09-08 15:27 cinap_lenrek
2007-09-08 16:49 ` erik quanstrom
2007-09-08 17:07 ` cinap_lenrek
2007-09-08 19:08 ` cinap_lenrek
2007-09-08 21:45 ` John Soros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d375e920709090622k2441b98fsf6be8a04282e139d@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).