From: NeilBrown <neilb@suse.de>
To: Markus Stockhausen <stockhausen@collogia.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies
Date: Wed, 20 Aug 2014 19:19:15 +1000 [thread overview]
Message-ID: <20140820191915.088eaa12@notabene.brown> (raw)
In-Reply-To: <12EF8D94C6F8734FB2FF37B9FBEDD1735863EE95@EXCHANGE.collogia.de>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On Wed, 20 Aug 2014 08:13:27 +0000 Markus Stockhausen
<stockhausen@collogia.de> wrote:
> > Von: NeilBrown [neilb@suse.de]
> > Gesendet: Mittwoch, 20. August 2014 05:36
> > An: Markus Stockhausen
> > Cc: linux-raid@vger.kernel.org
> > Betreff: Re: [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies
> > ...
> > For future reference:
> > - put "md" at the start of the subject line. e.g. "md/raid5:"
> > - use "git show --format=email" or some other incantation which
> > avoids indenting the description. Also avoid the "commit"
> > line. Author: and Date: are redundant but I don't think they
> > are actually hurting.
> > - Be sure to include a Signed-off-by: line. Find and read the DCO
> > (Developer's Certificate of Origin) to know what that means.
> > This patch is sufficiently trivial that I won't insist, but it is a good
> > habit to get into (git commit --amend --sign --no-edit)
>
> Hi Neil,
>
> Good to know. Adapted my generator scripts for that. Do you want me to
> resend the RMW patches that way?
Probably - I definitely want the s-o-b. Wait 'til I've had a change to have
a look though.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-08-20 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 9:37 [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies Markus Stockhausen
2014-08-20 3:36 ` NeilBrown
2014-08-20 8:13 ` AW: " Markus Stockhausen
2014-08-20 9:19 ` NeilBrown [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=20140820191915.088eaa12@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=stockhausen@collogia.de \
/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;
as well as URLs for NNTP newsgroup(s).