From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] replica/updatedb
Date: Wed, 7 Mar 2007 11:00:14 -0500 [thread overview]
Message-ID: <ee9e417a0703070800i545b0abw807c81885683b3e0@mail.gmail.com> (raw)
In-Reply-To: <07f076c821c5ff2efca16357f198075a@coraid.com>
On 3/7/07, erik quanstrom <quanstro@coraid.com> wrote:
> i'm using updatedb on two successive days in a dump
> where $path on day n-1 was a file and $path on day n
> was a directory. updatedb generates an 'm' (modified
> stat) line for this case. this seems wrong to me.
> i would think that it should generate a 'd' (delete) followed
> by a 'c' (create) pair. although i'm sure an argument could
> be made the other way.
>
> i'm leaning toward changing updatedb. is there a better
> argument for fixing the consumer?
you should fix updatedb. if this had happened on sources
then you would need to fix applylog too, since lots of people
would need to be able to apply the existing log.
russ
prev parent reply other threads:[~2007-03-07 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 13:47 erik quanstrom
2007-03-07 16:00 ` Russ Cox [this message]
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=ee9e417a0703070800i545b0abw807c81885683b3e0@mail.gmail.com \
--to=rsc@swtch.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).