Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
Cc: linux-ide@vger.kernel.org
Subject: Re: PATCH: Put the new API functions in the header files
Date: Fri, 05 Nov 2004 23:36:35 +0000	[thread overview]
Message-ID: <1099697793.5567.85.camel@localhost.localdomain> (raw)
In-Reply-To: <200411052302.50280.bzolnier@elka.pw.edu.pl>

On Gwe, 2004-11-05 at 22:02, Bartlomiej Zolnierkiewicz wrote:
> * there is no ordering of your patches
> * they are splitted on file boundary not change boundary
>   (ie. appling one patch leaves you with kernel which won't compile)

Well I could send you bigger pieces if you want but you objected to that
last time.

> * they are whitespace damaged as usual

Well if you want to be a bigot about the old trailing space caused by
editor auto indenting feel free 8)



  reply	other threads:[~2004-11-06  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 16:32 PATCH: Put the new API functions in the header files Alan Cox
2004-11-05 22:02 ` Bartlomiej Zolnierkiewicz
2004-11-05 23:36   ` Alan Cox [this message]
2004-11-06  0:51     ` Bartlomiej Zolnierkiewicz

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=1099697793.5567.85.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@elka.pw.edu.pl \
    --cc=linux-ide@vger.kernel.org \
    /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