Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S317478AbSGOPfL>; Mon, 15 Jul 2002 11:35:11 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S317503AbSGOPfK>; Mon, 15 Jul 2002 11:35:10 -0400
Received: from lockupnat.curl.com ([216.230.83.254]:4599 "EHLO
	egghead.curl.com") by vger.kernel.org with ESMTP id <S317478AbSGOPfJ>;
	Mon, 15 Jul 2002 11:35:09 -0400
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
       Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Subject: Re: [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories on NFS mounts
References: <20020715075221.GC21470@uncarved.com>
	<Pine.LNX.3.95.1020715084232.22834A-100000@chaos.analogic.com>
	<20020715133507.GF32155@merlin.emma.line.org>
	<s5gwurxt59x.fsf@egghead.curl.com>
	<1026749802.30202.13.camel@irongate.swansea.linux.org.uk>
From: "Patrick J. LoPresti" <patl@curl.com>
Date: 15 Jul 2002 11:38:04 -0400
In-Reply-To: <1026749802.30202.13.camel@irongate.swansea.linux.org.uk>
Message-ID: <s5ghej1t31f.fsf@egghead.curl.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1328
Lines: 27

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> Linus has explicitly stated what fsync on a directory does, during
> several of the thousands of cycling repeated flamewars generated by MTA
> authors
> 
> If that isnt definitive I don't know what is

Documentation/fsync.txt would be better.

I mean, suppose I write to some MTA's authors to inform them that
their product is "broken on Linux" and telling them how to fix it.
They might think I am nuts, or that this behavior is an implementation
coincidence.  (Some of them even seem to think Linux is not complying
with the relevant standards.  That there is even an argument here
means that the standards themselves are broken; standards are supposed
to be very clear.)

To where should I refer these authors to convince them that this
really is how Linux behaves, by definition, now and forever?  Should I
point them at the flamewars in various mailing list archives?  Should
I suggest they write to Linus personally?

I would rather refer them to Documentation/fsync.txt.  Do you agree?
Would you accept a patch to add it?

 - Pat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/