From: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: PATCH: Put the new API functions in the header files
Date: Sat, 6 Nov 2004 01:51:28 +0100 [thread overview]
Message-ID: <200411060151.28742.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <1099697793.5567.85.camel@localhost.localdomain>
On Saturday 06 November 2004 00:36, Alan Cox wrote:
> 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.
all or nothing...
> > * 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)
sigh
prev parent reply other threads:[~2004-11-06 0:47 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
2004-11-06 0:51 ` Bartlomiej Zolnierkiewicz [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=200411060151.28742.bzolnier@elka.pw.edu.pl \
--to=bzolnier@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--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