All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>, linux-kernel@vger.kernel.org
Subject: Re: Htree directory index for Ext2, updated
Date: Sat, 18 May 2002 02:49:44 +0200	[thread overview]
Message-ID: <E178sPr-0000Be-00@starship> (raw)
In-Reply-To: <200205170422.g4H4M5q295551@saturn.cs.uml.edu> <E178a8G-00005D-00@starship> <20020517084327.A20573@flint.arm.linux.org.uk>

On Friday 17 May 2002 09:43, Russell King wrote:
> On Fri, May 17, 2002 at 07:18:23AM +0200, Daniel Phillips wrote:
> > I think you're saying that patch is broken by design.  And what's the
> > standard argument for not fixing it?
> 
> There are a set of guidelines for generating patches given in the patch
> 2.5 manpage.  I would suggest people go and read them.  The section is
> marked: "NOTES FOR PATCH SENDERS"

I will go as far as agreeing that this is a standard argument.

-- 
Daniel

      reply	other threads:[~2002-05-18  0:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17  0:34 Htree directory index for Ext2, updated Daniel Phillips
2002-05-17  4:22 ` Albert D. Cahalan
2002-05-17  5:18   ` Daniel Phillips
2002-05-17  7:36     ` Albert D. Cahalan
2002-05-18  1:21       ` Daniel Phillips
2002-05-18  5:34         ` Andreas Dilger
2002-05-18  5:44           ` Daniel Phillips
2002-05-18  5:57             ` Kai Germaschewski
2002-05-18  5:58             ` Andreas Dilger
2002-05-18  6:13               ` Daniel Phillips
2002-05-18 17:26                 ` Andreas Dilger
2002-05-22  9:43                   ` Daniel Phillips
2002-05-22 10:23                     ` Andreas Dilger
2002-05-22 14:40                       ` Larry McVoy
2002-05-18  6:22               ` Daniel Phillips
2002-05-17  7:43     ` Russell King
2002-05-18  0:49       ` Daniel Phillips [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=E178sPr-0000Be-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.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 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.