From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: mtk.manpages@gmail.com, linux-kernel@vger.kernel.org, hch@lst.de,
miklos@szeredi.hu, viro@zeniv.linux.org.uk, jamie@shareable.org,
drepper@redhat.com, linux-fsdevel@vger.kernel.org,
subrata@linux.vnet.ibm.com
Subject: Re: utimensat() non-conformances and fixes [v4] (patch)
Date: Tue, 3 Jun 2008 13:22:31 -0700 [thread overview]
Message-ID: <20080603132231.1430f812.akpm@linux-foundation.org> (raw)
In-Reply-To: <4845A606.6070005@gmail.com>
On Tue, 03 Jun 2008 22:13:58 +0200
Michael Kerrisk <mtk.manpages@googlemail.com> wrote:
> This patch fixes all of the utimensat() bugs outlined in my
> previous mail.
>
> I could have split the patch out into a few pieces, but given
> that it is not long, and all against a single file, I've made
> one patch. Let me know if you would like separate patches for
> the pieces below.
Well I think it would have been better, really.
Right now someone (apparently me) needs to take the text from
"utimensat() non-conformances and fixes [v4] (overview)" and weave it
together with the text from "utimensat() non-conformances and fixes
[v4] (patch)" to produce a vaguely coherent changelog.
It all would be much saner and cleaner if each of these changes was in
a self-contained diff which had its own standalone changelog, no?
next prev parent reply other threads:[~2008-06-03 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48454F1D.6060507@gmail.com>
2008-06-03 20:13 ` utimensat() non-conformances and fixes [v4] (patch) Michael Kerrisk
2008-06-03 20:22 ` Andrew Morton [this message]
2008-06-03 20:29 ` Michael Kerrisk
2008-06-03 20:14 ` utimensat() non-conformances and fixes [v4] (test suite) Michael Kerrisk
[not found] ` <484569E5.5090108@gmail.com>
2008-06-03 20:15 ` utimensat() non-conformances and fixes [v4] (test results) Michael Kerrisk
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=20080603132231.1430f812.akpm@linux-foundation.org \
--to=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=mtk.manpages@gmail.com \
--cc=mtk.manpages@googlemail.com \
--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).