[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m11vr5jrba.fsf@fess.ebiederm.org>
Date: Sun, 03 May 2009 23:49:29 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: paulmck@...ux.vnet.ibm.com
Cc: tridge@...ba.org, Al Viro <viro@...IV.linux.org.uk>,
Pavel Machek <pavel@....cz>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <matthew@....cx>,
Steve French <smfrench@...il.com>,
Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
Ogawa Hirofumi <hirofumi@...l.parknet.co.jp>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Michael Tokarev <mjt@....msk.ru>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> writes:
> On Sun, May 03, 2009 at 10:42:52PM -0700, Eric W. Biederman wrote:
>> The only reason I can see for not ultimately talking about things publicly
>> is if this is one company making shady deals with another company in which
>> case I do not see why the maintenance burden for those decision should
>> fall on the linux community as a whole.
>
> Another reason is that past experience would indicate that anything we
> say in public and and will be used against us.
Which is a fine reason to be careful what you say, and to say
reasonable things. It is not a reason to submit a patch without
justification.
If the reason for submitting a patch is not sufficiently good to be
held to then it appears insufficient to merge the patch.
Why should the commit to a position at your urging that you aren't
willing to commit to?
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists