From: Borislav Petkov <bp@alien8.de>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Rob Landley <rob@landley.net>
Subject: Re: [PATCH 2/3] SubmittingPatches: Add recommendation for mailing list references
Date: Sun, 15 Dec 2013 22:17:01 +0100 [thread overview]
Message-ID: <20131215211701.GC32667@pd.tnic> (raw)
In-Reply-To: <20131215205939.GA11125@leaf>
On Sun, Dec 15, 2013 at 12:59:40PM -0800, Josh Triplett wrote:
> SubmittingPatches already mentions referencing bugs fixed by a commit,
> but doesn't mention citing relevant mailing list discussions. Add a
> note to that effect, along with a recommendation to use the
> https://lkml.kernel.org/ redirector.
>
> Portions based on text from git's SubmittingPatches.
>
> Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Yep.
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-12-15 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 20:59 [PATCH 2/3] SubmittingPatches: Add recommendation for mailing list references Josh Triplett
2013-12-15 21:17 ` Borislav Petkov [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=20131215211701.GC32667@pd.tnic \
--to=bp@alien8.de \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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