From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andries.Brouwer@cwi.nl, akpm@digeo.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch?] truncate and timestamps
Date: 27 May 2003 00:42:35 +0100 [thread overview]
Message-ID: <1053992553.17151.18.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030523011751.GC14406@parcelfarce.linux.theplanet.co.uk>
On Gwe, 2003-05-23 at 02:17, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> Andries had shown that there is _no_ consensus. Ergo, POSIX can take
> a hike and we should go with the behaviour convenient for us. It's that
> simple...
Skipping the update on a truncate not changing size is a performance win
although not a very useful one. I don't think we can ignore the standard
however. For one it simply means all the vendors have to fix it so they
can sell to Government etc.
Now we can certainly put the fix in -every- vendor tree on the planet
and not base, I'm just not sure for something so trivial it isnt better
just to fix it to the spec *or* beat the spec authors up to fix the
spec.
next prev parent reply other threads:[~2003-05-27 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 0:17 Andries.Brouwer
2003-05-23 0:30 ` Linus Torvalds
2003-05-23 1:17 ` viro
2003-05-23 2:42 ` Andrew Morton
2003-05-23 5:11 ` Trond Myklebust
2003-05-23 5:25 ` Trond Myklebust
2003-05-23 3:14 ` David Schwartz
2003-05-26 23:42 ` Alan Cox [this message]
2003-05-27 1:17 ` Andrew Morton
2003-05-23 18:02 ` Kai Henningsen
2003-05-23 19:07 ` Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 19:09 Andries.Brouwer
2003-05-22 23:20 ` Andrew Morton
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=1053992553.17151.18.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®