From: Al Viro <viro@ZenIV.linux.org.uk>
To: tridge@samba.org
Cc: Pavel Machek <pavel@ucw.cz>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <matthew@wil.cx>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Steve French <smfrench@gmail.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
Ogawa Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Michael Tokarev <mjt@tls.msk.ru>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option
Date: Sun, 3 May 2009 23:56:16 +0100 [thread overview]
Message-ID: <20090503225616.GD8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <18942.6593.544212.571063@samba.org>
On Mon, May 04, 2009 at 08:25:05AM +1000, tridge@samba.org wrote:
> Hi Pavel,
>
> > Well if they are obvious, please get us someone who _can_ discuss them
> > with us. Preferably a lawyer that can explain why the patch is
> > neccessary.
>
> I am trying to get that to happen, and I do realise that getting a
> lawyer to publicly explain the situation would be really
> worthwhile. Unfortunately lawyers are (mostly) very shy of making
> public statements of this type, because the legal consequences of
> making these statements can be non-trivial.
Practical consequences of establishing that kind of precedent (applying
a patch on the grounds of nothing but vague references to possibly
legal problems, with author explicitly refusing to explain exact reasons)
can also be non-trivial... And I'm not sure that it won't have legal
ones as well, while we are at it.
next prev parent reply other threads:[~2009-05-03 22:56 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:18 [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option Steve French
2009-05-01 21:01 ` Christoph Hellwig
2009-05-02 1:37 ` Paul E. McKenney
2009-05-02 1:59 ` Matthew Wilcox
2009-05-02 3:02 ` Steve French
2009-05-02 3:02 ` Steve French
2009-05-02 4:51 ` Paul E. McKenney
2009-05-02 9:15 ` tridge
2009-05-02 9:22 ` Christoph Hellwig
2009-05-02 9:30 ` tridge
2009-05-02 12:44 ` Christoph Hellwig
2009-05-03 21:57 ` Pavel Machek
2009-05-03 22:25 ` tridge
2009-05-03 22:56 ` Al Viro [this message]
2009-05-03 23:15 ` tridge
2009-05-04 5:42 ` Eric W. Biederman
2009-05-04 6:34 ` Paul E. McKenney
2009-05-04 6:49 ` Eric W. Biederman
2009-05-04 12:41 ` Paul E. McKenney
2009-05-04 12:44 ` Matthew Wilcox
2009-05-04 13:06 ` Paul E. McKenney
2009-05-04 13:21 ` Matthew Wilcox
2009-05-04 14:39 ` Paul E. McKenney
2009-05-04 15:08 ` Matthew Wilcox
2009-05-04 15:36 ` Dave Kleikamp
2009-05-04 15:59 ` Eric W. Biederman
2009-05-04 16:07 ` Dave Kleikamp
2009-05-04 16:30 ` Eric W. Biederman
2009-05-04 16:42 ` Paul E. McKenney
2009-05-04 17:18 ` Eric W. Biederman
2009-05-04 17:49 ` Paul E. McKenney
2009-05-04 17:54 ` Matthew Wilcox
2009-05-04 18:14 ` Paul E. McKenney
2009-05-04 18:17 ` Al Viro
2009-05-04 20:18 ` Paul E. McKenney
2009-05-04 17:06 ` Olivier Galibert
2009-05-04 17:27 ` Christoph Hellwig
2009-05-04 20:53 ` Chris Friesen
2009-05-04 23:03 ` Theodore Tso
2009-05-05 11:09 ` David Newall
2009-05-05 11:09 ` David Newall
2009-05-05 20:56 ` Valdis.Kletnieks
2009-05-05 21:04 ` Christoph Hellwig
2009-05-05 22:29 ` Steve French
2009-05-05 22:29 ` Steve French
2009-05-05 8:31 ` Zero-day exploit details (Was: Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option) David Newall
2009-05-04 16:11 ` [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option Paul E. McKenney
2009-05-04 15:38 ` Paul E. McKenney
2009-05-04 15:55 ` Matthew Wilcox
2009-05-04 16:10 ` Paul E. McKenney
2009-05-04 16:22 ` Matthew Wilcox
2009-05-04 22:12 ` Greg KH
2009-05-05 2:01 ` Matthew Wilcox
2009-05-05 2:11 ` Paul E. McKenney
2009-05-05 2:18 ` Matthew Wilcox
2009-05-05 2:18 ` Matthew Wilcox
2009-05-05 3:34 ` Paul E. McKenney
2009-05-05 3:34 ` Paul E. McKenney
2009-05-05 8:05 ` Valdis.Kletnieks
2009-05-05 15:35 ` Paul E. McKenney
2009-05-05 21:00 ` Valdis.Kletnieks
2009-05-05 21:56 ` Paul E. McKenney
2009-05-05 3:08 ` Valdis.Kletnieks
2009-05-04 15:55 ` Christoph Hellwig
2009-05-04 16:11 ` Paul E. McKenney
2009-05-04 15:40 ` Valdis.Kletnieks
2009-05-02 6:33 ` Christoph Hellwig
2009-05-02 2:12 ` Theodore Tso
2009-05-02 6:38 ` Christoph Hellwig
2009-05-02 6:38 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2009-05-01 17:41 Dave Kleikamp
2009-05-01 17:47 ` Christoph Hellwig
2009-05-01 18:12 ` Dave Kleikamp
2009-05-01 18:19 ` Michael Tokarev
2009-05-01 19:09 ` Dave Kleikamp
2009-05-01 18:30 ` Christoph Hellwig
2009-05-02 10:09 ` OGAWA Hirofumi
2009-05-02 10:14 ` OGAWA Hirofumi
2009-05-02 10:26 ` OGAWA Hirofumi
2009-05-02 10:41 ` tridge
2009-05-02 11:03 ` OGAWA Hirofumi
2009-05-02 11:13 ` tridge
2009-05-02 11:29 ` OGAWA Hirofumi
2009-05-02 11:41 ` tridge
2009-05-02 11:59 ` OGAWA Hirofumi
2009-05-02 12:15 ` tridge
2009-05-02 12:48 ` OGAWA Hirofumi
2009-05-02 13:06 ` tridge
2009-05-02 14:01 ` OGAWA Hirofumi
2009-05-27 12:05 ` vimal singh
2009-05-27 12:05 ` vimal singh
2009-05-27 23:57 ` tridge
2009-06-04 10:26 ` vimal singh
2009-06-04 10:26 ` vimal singh
2009-06-04 21:33 ` tridge
2009-05-02 10:20 ` tridge
2009-05-02 10:32 ` OGAWA Hirofumi
2009-05-03 21:56 ` Pavel Machek
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=20090503225616.GD8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mjt@tls.msk.ru \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pavel@ucw.cz \
--cc=shaggy@linux.vnet.ibm.com \
--cc=smfrench@gmail.com \
--cc=tridge@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.