From: James Bottomley <James.Bottomley@steeleye.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: fwd: [RFD] Explicitly documenting patch submission
Date: 25 May 2004 16:17:50 -0500 [thread overview]
Message-ID: <1085519871.1882.220.camel@mulgrave> (raw)
In-Reply-To: <1085421935.2780.21.camel@laptop.fenrus.com>
On Mon, 2004-05-24 at 13:05, Arjan van de Ven wrote:
> On Mon, 2004-05-24 at 19:35, James Bottomley wrote:
> > The original message from Linus is here:
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=108529494402563
> >
> > I've attached the text below as well. Unless anyone has strong
> > objections, we'll begin to use this "signed-off-by" tag for SCSI
> > submissions.
>
> Personally I don't think it's a good idea, nor do I think the RFD is
> done yet...
I don't thing the RFD is done yet either. I'm also not about to start
rejecting patches because they don't conform. However, I will be
accepting patches that do...
James
prev parent reply other threads:[~2004-05-25 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 17:35 fwd: [RFD] Explicitly documenting patch submission James Bottomley
2004-05-24 18:05 ` Arjan van de Ven
2004-05-25 21:17 ` James Bottomley [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=1085519871.1882.220.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=arjanv@redhat.com \
--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