From: Hans Reiser <reiser@namesys.com>
To: Anton Ertl <anton@mips.complang.tuwien.ac.at>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>,
vs@thebsh.namesys.com, jw schultz <jw@pegasys.ws>,
Alex Adriaanse <alex_a@caltech.edu>
Subject: Re: ReiserFS patch for updating ctimes of renamed files
Date: Tue, 14 Oct 2003 12:40:57 +0400 [thread overview]
Message-ID: <3F8BB699.3070404@namesys.com> (raw)
In-Reply-To: <2003Oct14.085717@a0.complang.tuwien.ac.at>
I looked again at the definition of the difference between ctime and
mtime on the stat man page, and I think that updating ctime in response
to rename is as reasonable as updating it in response to changing the
number of links.
Ok, we will conform, and I will accept the kindly donated patch, along
with Andrew's optimization of our evaluation of CURRENT_TIME. vs,
please add Andrew's suggested optimization and sent the result through
QA. Thanks to all for your good advice.
--
Hans
next prev parent reply other threads:[~2003-10-14 8:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Gr0H.1ol.5@gated-at.bofh.it>
2003-10-14 6:57 ` ReiserFS patch for updating ctimes of renamed files Anton Ertl
2003-10-14 8:40 ` Hans Reiser [this message]
2003-10-14 14:08 ` Alex Adriaanse
2003-10-25 14:42 ` Alex Adriaanse
[not found] <JIEIIHMANOCFHDAAHBHOMENJDAAA.alex_a@caltech.edu>
[not found] ` <3FBBA8A7.7090802@namesys.com>
[not found] ` <200311201746.15843.vs@namesys.com>
2003-11-23 4:22 ` Alex Adriaanse
2003-10-12 6:05 Alex Adriaanse
2003-10-12 7:14 ` jw schultz
2003-10-13 5:49 ` Hans Reiser
[not found] ` <20031013073154.GL8724@pegasys.ws>
2003-10-13 8:45 ` Hans Reiser
2003-10-14 2:37 ` Alex Adriaanse
2003-10-14 6:09 ` Hans Reiser
2003-10-14 6:49 ` jw schultz
2003-10-14 9:29 ` Jamie Lokier
2003-10-13 10:24 ` Andrew Morton
2003-10-14 6:13 ` Hans Reiser
2003-10-14 6:25 ` Andrew Morton
2003-10-14 6:30 ` Hans Reiser
2003-10-14 6:44 ` Andrew Morton
2003-10-14 7:09 ` jw schultz
2003-10-13 5:32 ` Hans Reiser
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=3F8BB699.3070404@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@zip.com.au \
--cc=alex_a@caltech.edu \
--cc=anton@mips.complang.tuwien.ac.at \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@thebsh.namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.