From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs corruption
Date: Tue, 25 Feb 2003 19:00:26 +0000 [thread overview]
Message-ID: <ece8829c562dbe203d90b91e16ed3818@vitanuova.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
none of the files are crucial - would it matter if i just clrid all
the mentioned adresses? (and then ran check f)
note: there are only three files mentioned (one 8 times and the others
once only); i'm kind of presuming it only mentions the duplication for
the second and subsequent instances.
[-- Attachment #2: Type: message/rfc822, Size: 1678 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs corruption
Date: Tue, 25 Feb 2003 13:41:20 -0500
Message-ID: <ddc17a96b9e719dff542689b17dd6b8f@plan9.bell-labs.com>
if it tells you the files that have duplicated addresses
you could clri one or both and then check f.
next reply other threads:[~2003-02-25 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 19:00 rog [this message]
2003-02-25 19:08 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 18:35 rog
2003-02-25 18:41 ` Russ Cox
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=ece8829c562dbe203d90b91e16ed3818@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).