From: Theodore Ts'o <tytso@mit.edu>
To: Daniel Phillips <daniel@phunq.net>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Pavel Machek <pavel@ucw.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [RFC] Tux3 for review
Date: Tue, 24 Jun 2014 06:59:40 -0400 [thread overview]
Message-ID: <20140624105940.GH14887@thunk.org> (raw)
In-Reply-To: <79582b70-6111-49f5-a1a9-f5701854e199@phunq.net>
On Tue, Jun 24, 2014 at 02:10:52AM -0700, Daniel Phillips wrote:
>
> That makes sense, because the patches to transform our workarounds
> into shiny new kernel hooks are still in progress, as I said. I would
> appreciate the courtesy of being permitted to take the time to do the
> work to the necessary quality without being subjected to endless
> carping about when the patches will be posted.
The feedback which you have been getting, fairly consistently I
believe, is that it is the shiny new kernel hooks that need to be
reviewed, not the workarounds. I don't think it's a matter of people
not being willing to give you the time to do this work (take all the
time you need!); but rather that it's premature for you to be asking
for tux3 to be merged before those patches have been posted and
reviewed and found to be shiny.
Best regards,
- Ted
next prev parent reply other threads:[~2014-06-24 10:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 0:50 [RFC] Tux3 for review Daniel Phillips
2014-05-17 0:50 ` Daniel Phillips
2014-05-17 5:09 ` Martin Steigerwald
2014-05-17 5:09 ` Martin Steigerwald
2014-05-17 5:29 ` Daniel Phillips
2014-05-17 5:29 ` Daniel Phillips
2014-05-20 6:56 ` Daniel Phillips
2014-05-18 23:55 ` Dave Chinner
2014-05-20 0:55 ` Daniel Phillips
2014-05-20 0:55 ` Daniel Phillips
2014-05-20 3:18 ` Dave Chinner
2014-05-20 3:18 ` Dave Chinner
2014-05-20 5:41 ` Daniel Phillips
2014-05-20 17:25 ` Daniel Phillips
2014-05-20 17:25 ` Daniel Phillips
2014-06-13 10:32 ` Pavel Machek
2014-06-13 17:49 ` Daniel Phillips
2014-06-13 20:20 ` Pavel Machek
2014-06-15 21:41 ` Daniel Phillips
2014-06-16 15:25 ` James Bottomley
2014-06-19 8:21 ` Pavel Machek
2014-06-19 9:26 ` Lukáš Czerner
2014-06-19 21:58 ` Daniel Phillips
2014-06-19 21:58 ` Daniel Phillips
2014-06-21 19:29 ` James Bottomley
2014-06-22 1:06 ` Dave Chinner
2014-06-24 11:16 ` Daniel Phillips
2014-06-22 3:32 ` Daniel Phillips
2014-06-22 14:43 ` James Bottomley
[not found] ` <522aee97-34e7-4adc-adf2-c9b73aa0ef36@phunq.net>
2014-06-24 4:41 ` James Bottomley
2014-06-24 9:10 ` Daniel Phillips
2014-06-24 10:59 ` Theodore Ts'o [this message]
2014-06-24 11:27 ` Daniel Phillips
2014-06-24 11:52 ` James Bottomley
2014-06-24 12:10 ` Daniel Phillips
2014-06-22 18:34 ` Theodore Ts'o
2014-06-24 0:31 ` Daniel Phillips
2014-06-24 0:19 ` Daniel Phillips
2014-05-22 9:52 ` Dongsu Park
2014-05-23 8:21 ` Daniel Phillips
2014-05-23 8:21 ` Daniel Phillips
2014-06-19 16:24 ` Josef Bacik
2014-06-19 16:24 ` Josef Bacik
2014-06-19 22:14 ` Daniel Phillips
2014-06-19 22:14 ` Daniel Phillips
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=20140624105940.GH14887@thunk.org \
--to=tytso@mit.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=daniel@phunq.net \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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.