From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fossil; is the time right?
Date: Fri, 14 Mar 2003 15:10:54 +0000 [thread overview]
Message-ID: <df93997c67f86fc16026e2a9ca7eca1d@vitanuova.com> (raw)
> But I know that if I dont sync by hand using the console
> I loose some blocks (some of the last changes may be missing).
that's understandable. at least in that case at least the directory
structure should remain intact. (a sync for venti and for fossil that
blocked until all writes were complete would be helpful, i guess).
i was mostly concerned about the possibility that one might
potentially lose a whole tree if the block representing the root of
that tree was lost in transit.
next reply other threads:[~2003-03-14 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 15:10 rog [this message]
2003-03-14 15:13 ` Fco.J.Ballesteros
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 13:39 rog
2003-03-14 14:57 ` Fco.J.Ballesteros
2003-03-14 19:00 ` Russ Cox
2003-03-14 23:54 ` Geoff Collyer
2003-03-14 9:59 Dan Cross
2003-03-14 12:21 ` Fco.J.Ballesteros
2003-03-14 16:16 ` rob pike, esq.
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=df93997c67f86fc16026e2a9ca7eca1d@vitanuova.com \
--to=rog@vitanuova.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).