public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: <Tudor.Ambarus@microchip•com>
Cc: <vigneshr@ti•com>, <linux-next@vger•kernel.org>,
	<linux-kernel@vger•kernel.org>,
	<sergei.shtylyov@cogentembedded•com>
Subject: Re: linux-next: Fixes tag needs some work in the spi-nor tree
Date: Fri, 29 May 2020 19:48:11 +1000	[thread overview]
Message-ID: <20200529194811.45f0f5b4@canb.auug.org.au> (raw)
In-Reply-To: <132770930.czcBmXCZeL@192.168.0.120>

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Hi,

On Fri, 29 May 2020 07:31:47 +0000 <Tudor.Ambarus@microchip•com> wrote:
>
> Right. Maybe it is worth to add this kind of check in checkpatch.pl. One can 
> generate the Fixes tag by adding an alias in .gitconfig:
> 
> [alias]
>         fixes = show --format='Fixes: %h (\"%s\")' -s

I usually suggest

	git log -1 --format='Fixes: %h ("%s")' <SHA>

but pretty much the same.  The trick is to make sure you have a new
enough version of git and make sure that core.abbrev is not set (or set
to "auto").
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-29  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 21:06 linux-next: Fixes tag needs some work in the spi-nor tree Stephen Rothwell
2020-05-29  7:31 ` Tudor.Ambarus
2020-05-29  9:48   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-28 22:10 Stephen Rothwell

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=20200529194811.45f0f5b4@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=Tudor.Ambarus@microchip$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sergei.shtylyov@cogentembedded$(echo .)com \
    --cc=vigneshr@ti$(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