From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@lst•de>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Ming Lei <ming.lei@redhat•com>
Subject: Re: linux-next: Fixes tags need some work in the dma-mapping-fixes tree
Date: Wed, 23 Jan 2019 23:13:59 +1100 [thread overview]
Message-ID: <20190123231359.286ac584@canb.auug.org.au> (raw)
In-Reply-To: <20190123230915.18046ca7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Hi Christoph,
On Wed, 23 Jan 2019 23:09:15 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> On Wed, 23 Jan 2019 08:19:33 +0100 Christoph Hellwig <hch@lst•de> wrote:
> >
> > On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> > > - SHA1 should be at least 12 digits long
> >
> > When did we decide on that? As far as I know it was bumped to 10
> > a while ago. 12 basically makes the line even more unreadable.
>
> From Documentation//process/submitting-patches.rst:
>
> "If your patch fixes a bug in a specific commit, e.g. you found an issue using
> ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
> the SHA-1 ID, and the one line summary."
That paragraph was added by commit
8401aa1f59975 ("Documentation/SubmittingPatches: describe the Fixes: tag")
commited by Linus on 2014-06-07 (before it got moved to the .rst file).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-23 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:47 linux-next: Fixes tags need some work in the dma-mapping-fixes tree Stephen Rothwell
2019-01-23 7:19 ` Christoph Hellwig
2019-01-23 12:09 ` Stephen Rothwell
2019-01-23 12:13 ` Stephen Rothwell [this message]
2019-01-23 10:50 ` Thierry Reding
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=20190123231359.286ac584@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ming.lei@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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