From: Kalle Valo <kvalo@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the v4l-dvb-fixes tree
Date: Mon, 17 Jul 2023 18:58:28 +0300 [thread overview]
Message-ID: <87jzuy34yj.fsf@kernel.org> (raw)
In-Reply-To: <ZLTsXUFZy4Iggk5u@kekkonen.localdomain> (Sakari Ailus's message of "Mon, 17 Jul 2023 07:23:09 +0000")
Sakari Ailus <sakari.ailus@linux.intel.com> writes:
> On Fri, Jul 14, 2023 at 08:38:25AM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> In commit
>>
>> b0b43354c345 ("media: tc358746: Address compiler warnings")
>>
>> Fixes tag
>>
>> Fixes: 80a21da3605 ("media: tc358746: add Toshiba TC358746 Parallel to CSI-2 bridge driver")
>>
>> has these problem(s):
>>
>> - SHA1 should be at least 12 digits long
>> This can be fixed for the future by setting core.abbrev to 12 (or
>> more) or (for git v2.11 or later) just making sure it is not set
>> (or set to "auto").
>>
>> Also, please keep all the commit message tags together at the end of
>> the commit message.
>
> Apologies for this, I guess I've removed one character too many from the
> hash.
>
> I'll switch to a script (or alias) to do this. It'd be, though, helpful if
> git could do this on its own.
Are you asking for git to create the Fixes tag? The documentation has
has a tip using --pretty=fixes which is quite handy:
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-07-17 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:38 linux-next: Fixes tag needs some work in the v4l-dvb-fixes tree Stephen Rothwell
2023-07-17 7:23 ` Sakari Ailus
2023-07-17 15:58 ` Kalle Valo [this message]
2023-07-18 6:09 ` Sakari Ailus
-- strict thread matches above, loose matches on Subject: below --
2021-01-12 20:44 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=87jzuy34yj.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.