From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ismael Ferreras Morezuelas <swyterzone@gmail.com>,
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 input-current tree
Date: Tue, 23 May 2023 17:40:18 -0700 [thread overview]
Message-ID: <ZG1c8l8uprzkcjBP@google.com> (raw)
In-Reply-To: <20230524081200.1badf8cb@canb.auug.org.au>
On Wed, May 24, 2023 at 08:12:00AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> feee70f45686 ("Input: xpad - delete a Razer DeathAdder mouse VID/PID entry")
>
> Fixes tag
>
> Fixes: f554f619b70 ("Input: xpad - sync device IDs with xboxdrv")
>
> 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").
Oops. Oh, well. I do not rewind my for-linus branch unless in extreme
circumstances, so it will have to stay this way. The tag still resolves
to the right commit, so not much harm done.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2023-05-24 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 22:12 linux-next: Fixes tag needs some work in the input-current tree Stephen Rothwell
2023-05-24 0:40 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-28 6:54 Stephen Rothwell
2019-01-24 11:09 Stephen Rothwell
2019-01-25 23:56 ` Dmitry Torokhov
2019-01-25 23:58 ` Dmitry Torokhov
2019-01-26 9:16 ` Lubomir Rintel
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=ZG1c8l8uprzkcjBP@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=swyterzone@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).