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
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
