linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Wim Coekaerts <wim.coekaerts@oracle.com>
Cc: Anton Blanchard <anton@samba.org>, Andrew Morton <akpm@osdl.org>,
	bug-coreutils@gnu.org, linux-kernel@vger.kernel.org,
	Andy Isaacson <adi@hexapodia.org>
Subject: Re: dd PATCH: add conv=direct
Date: Sat, 10 Apr 2004 23:28:16 +0200	[thread overview]
Message-ID: <85ekqvmsjz.fsf@pi.meyering.net> (raw)
In-Reply-To: <20040409014244.GO20863@ca-server1.us.oracle.com> (Wim Coekaerts's message of "Thu, 8 Apr 2004 18:42:44 -0700")

Wim Coekaerts <wim.coekaerts@oracle.com> wrote:
> philip copeland did a whole set of patches for coreutils to allow
> directio for both read write and mixed sizes even
> the rpm is at
> http://oss.oracle.com/projects/ocfs/files/source/RHAT/RHAS3/coreutils-4.5.3-33.src.rpm,

Thanks for the pointer.
FYI, that URL didn't work for me.  This one did:

http://oss.oracle.com/projects/ocfs/dist/files/source/RHAT/RHAS3/coreutils-4.5.3-33.src.rpm

Whoever maintains that code should consider merging their changes with
something newer.  There are over 500 lines of NEWS entries alone for the
coreutils releases that have been made since 4.5.3.

Besides, those patches have portability and robustness problems,
and they aren't even based on coreutils-4.5.3.  Maybe they're
based on some vendor's version of coreutils?

> I think he took it up with the maintainers but so far had no luck

As far as I know, no one ever submitted such O_DIRECT-based patches
to me or any of the bug-*@gnu.org mailing lists.

The only pending O_DIRECT-based patch is one for shred.

Clean, complete, and well-justified patches usually go in pretty quickly.

  reply	other threads:[~2004-04-10 21:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 22:03 dd PATCH: add conv=direct Andy Isaacson
2004-04-07  0:33 ` Andrew Morton
2004-04-07 16:21   ` Bruce Allen
2004-04-07 16:42     ` Andrew Morton
2004-04-07 17:31   ` Andy Isaacson
2004-04-07 18:18     ` Andrew Morton
2004-04-07 19:24       ` Andy Isaacson
2004-04-07 19:34         ` Andrew Morton
2004-04-07 19:47           ` Andy Isaacson
2004-04-07 20:03             ` Andrew Morton
2004-04-07 20:43               ` Andy Isaacson
2004-04-07 21:00                 ` Valdis.Kletnieks
2004-04-07 21:35                 ` Bruce Allen
2004-04-08  6:56                   ` Paul Eggert
2004-04-08 11:07                     ` Jim Meyering
2004-04-08 19:32                       ` Paul Eggert
2004-04-08 19:51                         ` Paul Jarc
2004-04-08 21:34                         ` Jim Meyering
2004-04-08 16:23                     ` Philippe Troin
2004-04-08 20:20                       ` dd patch to remove noctty Paul Eggert
2004-04-08 21:40                         ` Jim Meyering
2004-04-09  0:37             ` dd PATCH: add conv=direct Anton Blanchard
2004-04-09  1:42               ` Wim Coekaerts
2004-04-10 21:28                 ` Jim Meyering [this message]
2004-04-07 20:46       ` Paul Eggert
2004-04-07 21:06         ` Andrew Morton
2004-04-07 21:09         ` Andy Isaacson
2004-04-07 19:12     ` Miquel van Smoorenburg
2004-04-07 20:14       ` Andy Isaacson
2004-04-07 22:02 ` Nathan Straz
2004-04-07 22:09   ` Andy Isaacson
2004-04-08 11:44     ` Miquel van Smoorenburg

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=85ekqvmsjz.fsf@pi.meyering.net \
    --to=jim@meyering.net \
    --cc=adi@hexapodia.org \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=bug-coreutils@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wim.coekaerts@oracle.com \
    /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).