From: Jeff Garzik <jgarzik@pobox.com>
To: Brett Russ <russb@emc.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH libata-dev-2.6 01/03] libata: whitespace updates
Date: Thu, 24 Mar 2005 23:28:12 -0500 [thread overview]
Message-ID: <4243935C.5080607@pobox.com> (raw)
In-Reply-To: <20050323203514.DE0042D8@lns1032.lss.emc.com>
applied patches 1-3, thanks much.
Small administrivia request, though: after using my patch merging
script to merge your patches, I have to do the following things manually:
* delete diffstat output
* delete patch filename
* un-indent patch description text
It would be great if I didn't have to do those manual steps :)
On the other hand, I really like your "patch 0/N" email with a
description of the entire patchset. Keep sending those, thanks.
Everything else looks great.
Jeff
next prev parent reply other threads:[~2005-03-25 4:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 22:20 [PATCH libata-dev-2.6 00/05] libata: scsi error handling improvements Brett Russ
2005-03-17 22:20 ` [PATCH libata-dev-2.6 01/05] libata: AHCI tf_read() support Brett Russ
2005-03-17 22:20 ` [PATCH libata-dev-2.6 02/05] libata: AHCI error handling fix Brett Russ
2005-03-17 22:20 ` [PATCH libata-dev-2.6 03/05] libata: update ATA PT sense desc code Brett Russ
2005-03-23 5:10 ` Jeff Garzik
2005-03-17 22:20 ` [PATCH libata-dev-2.6 04/05] libata: support descriptor sense in ctrl page Brett Russ
2005-03-23 4:24 ` Jeff Garzik
2005-03-17 22:20 ` [PATCH libata-dev-2.6 05/05] libata: rework how CCs generated Brett Russ
2005-03-23 5:12 ` Jeff Garzik
2005-03-23 20:36 ` [PATCH libata-dev-2.6 00/03] libata: scsi error handling improvements Brett Russ
2005-03-23 20:39 ` [PATCH libata-dev-2.6 01/03] libata: whitespace updates Brett Russ
2005-03-25 4:28 ` Jeff Garzik [this message]
2005-03-23 20:42 ` [PATCH libata-dev-2.6 02/03] libata: create/use ata_dump_status() Brett Russ
2005-03-23 20:45 ` [PATCH libata-dev-2.6 03/03] libata: rework check condition handling Brett Russ
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=4243935C.5080607@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=russb@emc.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 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.