linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Nilmoni Deb <ndeb@ece.cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fs/ext2/namei.c: dir link/unlink bug? [Re: mv changes dir timestamp
Date: 01 Oct 2001 21:06:44 -0600	[thread overview]
Message-ID: <m1vghy3fln.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.3.96L.1011001150851.16650A-100000@d-alg.ece.cmu.edu>
In-Reply-To: <Pine.LNX.3.96L.1011001150851.16650A-100000@d-alg.ece.cmu.edu>

Nilmoni Deb <ndeb@ece.cmu.edu> writes:

> On 1 Oct 2001, Eric W. Biederman wrote:
> 
> > Or vice versa, as touch will also go back in time.
> 
> This is not a good idea because once the user has to remember the exact
> time stamp before the move and put that on the moved dir using touch.

You add a mv -p option to do it for you.
 
> > My question is which semantics are desirable, and why.  I conceed
> > that something has changed.  And that changing the functionality back
> > to the way it was before may be desireable.  But given that the
> > directory is in fact changed my gut reaction is that the new behavior
> > is more correct than the old behavior.
> 
> U r right but most users won't care too much about the ".." link inside
> each dir. Its the other files that really count. If the other files
> remain unchanged then they consider the dir as unchanged.

O.k. So nothing breaks and we just have a suprising change to more
correct behavior.  Given that I don't see the case for making a special
case in the code.  

Eric

  reply	other threads:[~2001-10-02  3:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96L.1010929125713.27868A-100000@d-alg.ece.cmu.edu>
2001-09-30  9:10 ` fs/ext2/namei.c: dir link/unlink bug? [Re: mv changes dir timestamp Jim Meyering
2001-09-30 18:58   ` Eric W. Biederman
2001-09-30 20:16     ` Nilmoni Deb
2001-10-01  8:25       ` Eric W. Biederman
2001-10-01 19:13         ` Nilmoni Deb
2001-10-02  3:06           ` Eric W. Biederman [this message]
2001-10-04  6:32       ` Bob Proulx
2001-10-04  7:50         ` Albert D. Cahalan
2001-10-04 17:24           ` Nilmoni Deb
2002-04-01  6:45     ` kernel 2.4.18 exception/bug during cd read operation Nilmoni Deb
2002-04-27 23:08   ` via82cxxx_audio bug in kernel-2.4.18 Nilmoni Deb

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=m1vghy3fln.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndeb@ece.cmu.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).