From: "Michael Kerrisk" <mtk-lkml@gmx.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: trond.myklebust@fys.uio.no, peterc@gelato.unsw.edu.au,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
matthew@wil.cx, michael.kerrisk@gmx.net
Subject: Re: fcntl(F GETLEASE) semantics??
Date: Thu, 11 Aug 2005 16:42:58 +0200 (MEST) [thread overview]
Message-ID: <31857.1123771378@www9.gmx.net> (raw)
In-Reply-To: <20050811142047.GE10030@fieldses.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 507 bytes --]
> Von: "J. Bruce Fields" <bfields@fieldses.org>
> In any case, I haven't seen a real argument for reverting to the old
> behaviour. I'd rather see an established standard, or a correct
^^^^^^^^^^^^^^^^^^^^
> real-world application that fails, not just some arbitrary test.
Agreed -- though I'd phrase it as "documented specification".
Cheers,
Michael
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
next prev parent reply other threads:[~2005-08-11 14:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 23:48 fcntl(F_GETLEASE) semantics?? Peter Chubb
2005-08-11 1:14 ` Trond Myklebust
2005-08-11 1:29 ` Peter Chubb
2005-08-11 8:14 ` fcntl(F GETLEASE) semantics?? Michael Kerrisk
2005-08-11 11:51 ` Trond Myklebust
2005-08-11 12:27 ` Michael Kerrisk
2005-08-11 12:49 ` Trond Myklebust
2005-08-11 13:22 ` Michael Kerrisk
2005-08-11 14:06 ` Trond Myklebust
2005-08-11 14:12 ` Trond Myklebust
2005-08-11 14:20 ` J. Bruce Fields
2005-08-11 14:42 ` Michael Kerrisk [this message]
2005-08-11 14:40 ` Michael Kerrisk
2005-08-11 15:06 ` Trond Myklebust
2005-08-11 15:25 ` Trond Myklebust
2005-08-11 14:10 ` Stephen Rothwell
2005-08-11 18:41 ` fcntl(F_GETLEASE) semantics?? Heikki Orsila
2005-08-11 18:56 ` Trond Myklebust
2005-08-11 19:02 ` Heikki Orsila
2005-08-11 19:15 ` Trond Myklebust
2005-08-11 19:23 ` Heikki Orsila
2005-08-11 19:31 ` Trond Myklebust
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=31857.1123771378@www9.gmx.net \
--to=mtk-lkml@gmx.net \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=michael.kerrisk@gmx.net \
--cc=peterc@gelato.unsw.edu.au \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@fys.uio.no \
/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®