From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
hch@lst.de, viro@zeniv.linux.org.uk, jamie@shareable.org,
drepper@redhat.com, linux-fsdevel@vger.kernel.org,
subrata@linux.vnet.ibm.com
Subject: Re: [patch 0/4 v2] vfs: fix utimensat() non-conformances to spec
Date: Wed, 4 Jun 2008 15:34:16 +0200 [thread overview]
Message-ID: <cfd18e0f0806040634p2c64d63es17aae9dfa9c2490c@mail.gmail.com> (raw)
In-Reply-To: <E1K3sxT-0000hy-9Z@pomaz-ex.szeredi.hu>
On Wed, Jun 4, 2008 at 3:23 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>> This patch series is a revised version of the patch series
>> that I sent yesterday to fix various utimensat()
>> non-conformances. Patches 1 and 2 are unchanged (and were
>> Acked by Miklos); patches 3 and 4 are revised following
>> comments by Miklos.
>>
>> As requested I've split the original patch
>> ("utimensat() non-conformances and fixes [v4] (patch)";
>> http://article.gmane.org/gmane.linux.file-systems/24325 )
>> into four parts. Ideally, these should be applied for
>> 2.6.26-rc, for the reasons outlined in my earlier mail
>> "utimensat() non-conformances and fixes [v4] (test results)",
>> http://article.gmane.org/gmane.linux.kernel/689411/ .
>>
>> The four patches can be applied independently, except that
>> patch 3 needs patch 2 to be applied first.
>
> ACK for all four patches.
>
> In patch 3/4 the indentation of that big "if" looks really horribly
> broken, but it will be cleaned out completely, so I won't complain...
Aargh -- true, I messed up the indentation!
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
prev parent reply other threads:[~2008-06-04 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 13:12 [patch 0/4 v2] vfs: fix utimensat() non-conformances to spec Michael Kerrisk
2008-06-04 13:22 ` Michael Kerrisk
2008-06-04 13:23 ` Miklos Szeredi
2008-06-04 13:34 ` Michael Kerrisk [this message]
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=cfd18e0f0806040634p2c64d63es17aae9dfa9c2490c@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=hch@lst.de \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=subrata@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).