From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@redhat.com>,
linux-ide@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: PATCH: IDE - fix various comments remove never changing ifdef
Date: Mon, 16 Aug 2004 19:27:18 +0100 [thread overview]
Message-ID: <1092680820.21069.0.camel@localhost.localdomain> (raw)
In-Reply-To: <200408162029.43797.bzolnier@elka.pw.edu.pl>
On Llu, 2004-08-16 at 19:29, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 15 August 2004 16:35, Alan Cox wrote:
> > No code changes in this patch just documenting
>
> If you want to remove FANCY_STATUS_DUMPS define please make
> a separate patch and remove it globally.
Will do.
prev parent reply other threads:[~2004-08-16 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 14:35 PATCH: IDE - fix various comments remove never changing ifdef Alan Cox
2004-08-16 18:29 ` Bartlomiej Zolnierkiewicz
2004-08-16 18:27 ` Alan Cox [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=1092680820.21069.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).