mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: drepper@redhat.com, viro@zeniv.linux.org.uk,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] utimensat() non-conformances and fixes [v3]
Date: Fri, 30 May 2008 21:43:59 +0200	[thread overview]
Message-ID: <cfd18e0f0805301243h7d862963o8320a2c1f48942ce@mail.gmail.com> (raw)
In-Reply-To: <cfd18e0f0805301124o5f217dden10726b268d05d81a@mail.gmail.com>

Miklos,

You omitted to answer my question, the last sentence below:

On Fri, May 30, 2008 at 8:24 PM, Michael Kerrisk
<mtk.manpages@googlemail.com> wrote:
> Miklos,
>
> I already fixed most of the isues with utimensat() in my previous
> version of the patch several days back, and that patch (probably
> still) applies against current mainline.
[...]
> This is a bug.  It is one of *several* bugs in the original
> implementation of the utimensat()/futimens() interface.  All of them
> should be fixed.  I have by now provided fixes for most of them.  (Not
> point 2 above, but with a little help that should be quickly fixed as
> well.)  At this point, I think you need to explain why you think those
> fixes shouldn't be applied.

Michael

-- 
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

  parent reply	other threads:[~2008-05-30 19:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16  8:31 [PATCH] utimensat() non-conformances and fixes -- version 2 Michael Kerrisk
2008-05-16  8:34 ` Michael Kerrisk
2008-05-16 16:59 ` Miklos Szeredi
2008-05-17 19:57   ` Michael Kerrisk
2008-05-19  9:50     ` Miklos Szeredi
2008-05-19 10:12       ` Miklos Szeredi
2008-05-19 12:24       ` Michael Kerrisk
2008-05-19 13:17         ` Miklos Szeredi
2008-05-30 15:34   ` [PATCH] utimensat() non-conformances and fixes [v3] Michael Kerrisk
2008-05-30 16:37     ` Miklos Szeredi
2008-05-30 18:24       ` Michael Kerrisk
2008-05-30 19:22         ` Miklos Szeredi
2008-05-30 19:32           ` Matthew Wilcox
2008-05-30 20:08             ` Miklos Szeredi
2008-05-30 19:43         ` Michael Kerrisk [this message]
2008-05-30 20:17           ` Miklos Szeredi
2008-05-31  5:28             ` Michael Kerrisk
2008-05-30 20:17         ` Andrew Morton
2008-05-31  5:44           ` Michael Kerrisk
2008-06-03 11:05     ` Michael Kerrisk
2008-06-03 11:13       ` Miklos Szeredi
2008-06-03 11:22         ` Al Viro
2008-06-03 11:27           ` Michael Kerrisk
2008-06-03 11:30             ` Jamie Lokier
2008-06-03 11:39               ` Michael Kerrisk
2008-06-03 11:49                 ` Al Viro
2008-06-03 11:58                   ` Al Viro
2008-06-03 12:01                   ` Jamie Lokier
2008-06-03 12:08                     ` Al Viro
2008-06-03 12:10                       ` Jamie Lokier
2008-06-03 12:16           ` Miklos Szeredi
2008-06-03 13:05             ` Al Viro
2008-06-03 11:52         ` 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=cfd18e0f0805301243h7d862963o8320a2c1f48942ce@mail.gmail.com \
    --to=mtk.manpages@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=drepper@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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

all inboxes | Powered by JetHome®