From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 1/20] aic94xx: Makefile
Date: Fri, 09 Sep 2005 15:48:17 -0400 [thread overview]
Message-ID: <4321E701.6060305@adaptec.com> (raw)
In-Reply-To: <20050909193541.GE24673@kvack.org>
Hi Ben,
I think I mentioned this in the Announcement 0/2:
http://www.geocities.com/ltuikov/
I'll soon move this to an Adaptec site.
Luben
On 09/09/05 15:35, Benjamin LaHaise wrote:
> A single file per patch is not really a patch split up. Patches should
> stand on their own, leaving the tree in a compilable functioning state
> during each step.
>
> -ben
>
next prev parent reply other threads:[~2005-09-09 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:32 [PATCH 2.6.13 1/20] aic94xx: Makefile Luben Tuikov
2005-09-09 19:35 ` Benjamin LaHaise
2005-09-09 19:48 ` Luben Tuikov [this message]
2005-09-09 20:11 ` Jeff Garzik
2005-09-09 20:18 ` Alexey Dobriyan
2005-09-09 20:12 ` Luben Tuikov
2005-09-09 20:14 ` viro
2005-09-10 12:26 ` Sam Ravnborg
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=4321E701.6060305@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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