From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Update on Fossil+Venti Stuff
Date: Wed, 21 Mar 2007 17:05:39 -0400 [thread overview]
Message-ID: <35035e8502a189df4e741fcf73c50c6d@coraid.com> (raw)
In-Reply-To: <9ab217670703211317o1958d9b3u647f6ac4fac758cd@mail.gmail.com>
On Wed Mar 21 16:24:59 EDT 2007, devon.odell@gmail.com wrote:
> I think everybody is a little confused about Fossil and Venti
> interaction. When I started this project, it was under the idea that
> Fossil was essentially a cache. It stored stuff, and when it either
> got too full or something else, it would start writing files out to
> Venti.
that "something else" is a snapshot archive which forces a flush to venti.
read the section on setting up snapshots (expecially the -a option) of
fossilcons(8). also, make sure fossil is really talking to venti.
>
> As I've been copying files over to my machine, I've noticed Fossil get
> fuller and fuller, but not sync anything over to Venti. Upon
> attempting to find information about this, we came up with:
>
> http://www.mail-archive.com/9fans@cse.psu.edu/msg03210.html
>
> Bruce doesn't sound too happy here,
if fossil fills between archival snapshots you are hosed. to the best of
my knowledge, fossil still behaves this way.
> and since Plan 9 doesn't have any
> version control or any commit logs (that I'm aware of), I can't tell
> whether any of these bugs have been fixed. Or, if so, whether they've
> been released.
while this is prima facia correct, sources keeps a archive of the sources
tree for every day. after "9fs sourcesdump; cd /n/sourcesdump/2005/0612"
would put you at the root of sources as it existed on 12 jun 2005.
if you want to see the changes in a particular file on sources over time
you can "9fs sources; cd /n/sources/plan9/sys/src/cmd/fossil; history 9srv.c".
you will get
Jan 28 11:32:21 EST 2006 9srv.c 3956 [rsc]
Jan 28 11:32:21 EST 2006 /n/sourcesdump/2007/0321/plan9/sys/src/cmd/fossil/9srv.c 3956 [rsc]
Feb 27 10:39:06 EST 2004 /n/sourcesdump/2006/0128/plan9/sys/src/cmd/fossil/9srv.c 3879 [jmk]
Oct 13 22:21:37 EDT 2003 /n/sourcesdump/2004/0227/plan9/sys/src/cmd/fossil/9srv.c 3682 [jmk]
Jun 15 15:02:14 EDT 2003 /n/sourcesdump/2003/1013/plan9/sys/src/cmd/fossil/9srv.c 3589 [rsc]
Feb 18 15:26:58 EST 2003 /n/sourcesdump/2003/0615/plan9/sys/src/cmd/fossil/9srv.c 3291 [rsc]
Jan 8 00:58:24 EST 2003 /n/sourcesdump/2003/0218/plan9/sys/src/cmd/fossil/9srv.c 3215 [rsc]
all patches applied from external sources are also recorded in /n/sources/patch/applied.
all pending external patches are in /n/sources/patch. internal labs changes
don't have a patch directory associated with them, but history will still show the
changes.
- erik
next prev parent reply other threads:[~2007-03-21 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 20:17 Devon H. O'Dell
2007-03-21 21:02 ` Martin Neubauer
2007-03-21 21:05 ` erik quanstrom [this message]
2007-03-21 21:24 ` Bakul Shah
2007-03-22 10:04 ` Richard Miller
2007-03-23 5:17 ` Devon H. O'Dell
2007-03-23 6:14 ` Martin Neubauer
2007-03-23 6:27 ` Devon H. O'Dell
2007-03-23 6:54 ` Martin Neubauer
2007-03-23 14:24 ` David Leimbach
2007-03-23 15:04 ` Devon H. O'Dell
2007-03-23 15:10 ` Richard Miller
2007-03-23 15:29 ` Devon H. O'Dell
2007-03-23 15:39 ` Richard Miller
2007-03-23 15:47 ` Devon H. O'Dell
2007-03-23 19:23 ` Steve Simon
2007-03-23 15:47 ` Richard Miller
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=35035e8502a189df4e741fcf73c50c6d@coraid.com \
--to=quanstro@coraid.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).