From: "Vesa Kaihlavirta" <vpkaihla@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] venti sync fixed?
Date: Tue, 2 Oct 2007 15:52:47 +0300 [thread overview]
Message-ID: <25acdd550710020552w47c3ae2au41a606272d7a223d@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi,
I installed a Plan 9 from a rather recent cd image (about two weeks old).
With fossil+venti. Everything seemed to work well, however, after the second
boot, I got the same venti sync problems as others have reported here.
Now. On IRC it was rumoured that this issue was found and perhaps fixed. Is
it? Could there have been a way for me to find out myself if this has been
fixed? Is there a CHANGELOG for kernel/fossil/venti?
--vk
[-- Attachment #2: Type: text/html, Size: 456 bytes --]
next reply other threads:[~2007-10-02 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 12:52 Vesa Kaihlavirta [this message]
2007-10-02 13:16 ` erik quanstrom
2007-10-02 13:29 ` Kernel Panic
2007-10-02 15:14 ` Vesa Kaihlavirta
2007-10-02 15:55 ` Bakul Shah
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=25acdd550710020552w47c3ae2au41a606272d7a223d@mail.gmail.com \
--to=vpkaihla@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).