From: Jeff Garzik <jgarzik@pobox.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [ANNOUNCE] Adaptec SAS/SATA device driver [03/27]
Date: Thu, 17 Feb 2005 14:17:52 -0500 [thread overview]
Message-ID: <4214EDE0.3020006@pobox.com> (raw)
In-Reply-To: <4214EBD2.3050409@adaptec.com>
Luben Tuikov wrote:
> On 02/17/05 14:03, Jeff Garzik wrote:
>
>> Luben,
>>
>> Your emails do not comply with the Linux kernel patch submission
>> format. Please read
>> http://linux.yyz.us/patch-format.html
>>
>> Most critical is rule number #5 (signed-off-by line), but also
>> important is rule number #1 (providing a useful subject line).
>
>
> Hi Jeff,
>
> Thanks for you reply. I'm well aware of the patch format.
> I wasn't sure about a different subject line since it it all part
> of a driver posting, "announce" rathern than "patch".
Yes, I understand that.
A key point is that it is impossible to differentiate your 27 patches,
from looking at them in a email summary. Putting a short summary of
each patch in the email subject line greatly assists those reviewing
your code.
> Yes, I forgot to add a signed off line. Sorry, but then again
> I didn't write the code, just presenting it. (#5. Sign your work...)
"sign your work" is more of a legal sign-off than a notation of
authorship. In some cases, a company lawyer may be the person included
in the signed-off-by line.
Jeff
next prev parent reply other threads:[~2005-02-17 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 17:35 [ANNOUNCE] Adaptec SAS/SATA device driver [03/27] Luben Tuikov
2005-02-17 19:03 ` Jeff Garzik
2005-02-17 19:09 ` Luben Tuikov
2005-02-17 19:17 ` Jeff Garzik [this message]
2005-02-17 19:22 ` Luben Tuikov
2005-02-17 21:39 ` Michael Tokarev
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=4214EDE0.3020006@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.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.