From: Borislav Petkov <bp@suse.de>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@suse.de>, Rob Landley <rob@landley.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 2/3] SubmittingPatches: Add recommendation for mailing list references
Date: Sat, 22 Feb 2014 23:39:47 +0100 [thread overview]
Message-ID: <20140222223947.GB2534@pd.tnic> (raw)
In-Reply-To: <20140222223038.GA4643@thin>
On Sat, Feb 22, 2014 at 02:30:38PM -0800, Josh Triplett wrote:
> > > If the patch fixes a logged bug entry, refer to that bug entry by
> > > -number and URL.
> > > +number and URL. If the patch follows from a mailing list discussion,
> > > +give a URL to the mailing list archive; use the https://lkml.kernel.org/
> > > +redirector with a Message-Id, to ensure that the links cannot become
> > > +stale.
> >
> > Some of us don't know what that looks like.
> > Could we have an example?
>
> https://lkml.kernel.org/ provides examples; I didn't want to duplicate
> that documentation.
Yeah, maybe you should say:
"If the patch follows from a mailing list discussion, give a URL to the
mailing list archive; use the https://lkml.kernel.org/ (usage examples
at that very URL) ... "
so that it is crystal clear.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-02-22 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 20:12 [PATCH RESEND 1/3] SubmittingPatches: Add style recommendation to use imperative descriptions Josh Triplett
2014-02-22 20:12 ` [PATCH RESEND 2/3] SubmittingPatches: Add recommendation for mailing list references Josh Triplett
2014-02-22 21:56 ` Randy Dunlap
2014-02-22 22:30 ` Josh Triplett
2014-02-22 22:39 ` Borislav Petkov [this message]
2014-02-22 23:04 ` Randy Dunlap
2014-02-22 20:12 ` [PATCH RESEND 3/3] SubmittingPatches: Document the use of git Josh Triplett
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=20140222223947.GB2534@pd.tnic \
--to=bp@suse.de \
--cc=akpm@linux-foundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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