From: James Smart <james.smart@emulex.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/19] lpfc 10.4.8000.0: Update lpfc version to driver version 10.4.8000.0
Date: Fri, 5 Sep 2014 09:31:43 -0400 [thread overview]
Message-ID: <5409BB3F.6040205@emulex.com> (raw)
In-Reply-To: <20140905053532.GA10457@infradead.org>
no problem, although if these rules were published, I would have tried
to do so earlier.
although - I do have a couple of questions.
On 9/5/2014 1:35 AM, Christoph Hellwig wrote:
> I've applied the series, but for next time can you make sure to follow
> the proper format:
>
> - remove the version number in every subject line
yeah - it's long
> - patches you resend from an original author should be unchanged,
> except that the From: lines moves into the mail body
So.. you do not want me to resolve merge conflicts or fuzz before posting ?
note: content did not change - only merged into my git tree and re-cut them.
> - patches that you send on with your maintainer hat on should be
> signed off by you, not just reviewed.
ok - but I guess I had a different interpretation of the meaning for
signed-by. I thought it conveyed an ownership and originality of
authorship of the content posted. As such, if I didn't contribute
anything in the patch, I shouldn't give anything other than a
reviewed-by indicating approval.
>
> not strictly required, but making my life a lot easier would be if all
> patches are sent by reply to the original mail. git-send-email does
> this, and it seems like the Emulex division supporting be2scsi has found
> a way to use it with the corporate email servers.
yep - although different countries have different logistics. But, I
should be able to get around this.
-- james
next prev parent reply other threads:[~2014-09-05 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 16:54 [PATCH 0/19] lpfc 10.4.8000.0: Update lpfc version to driver version 10.4.8000.0 James Smart
2014-09-05 5:35 ` Christoph Hellwig
2014-09-05 13:31 ` James Smart [this message]
2014-09-05 13:59 ` James Bottomley
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=5409BB3F.6040205@emulex.com \
--to=james.smart@emulex.com \
--cc=hch@infradead.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 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.