From: Andrew Donnellan <ajd@linux•ibm.com>
To: Jonathan Corbet <corbet@lwn•net>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: 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 jc_docs tree
Date: Fri, 26 Feb 2021 09:35:54 +1100 [thread overview]
Message-ID: <89ce7fd6-f71c-b9b2-febd-bbfafdd7b484@linux.ibm.com> (raw)
In-Reply-To: <87a6rrbze2.fsf@meer.lwn.net>
On 26/2/21 8:39 am, Jonathan Corbet wrote:
> Stephen Rothwell <sfr@canb•auug.org.au> writes:
>
>> Hi all,
>>
>> In commit
>>
>> 36eaf08fc283 ("docs: powerpc: Fix tables in syscall64-abi.rst")
>>
>> Fixes tag
>>
>> Fixes: 209b44c804c ("docs: powerpc: syscall64-abi.rst: fix a malformed table")
>>
>> has these problem(s):
>>
>> - SHA1 should be at least 12 digits long
>>
>> I don't think this is worth rebasing for, but in the future it can be
>> fixed 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").
>
> I made that tag by hand while "fixing" the changlog on that commit,
> which included the full ID. Obviously, counting to 12 is a challenging
> task for a slow guy like me...:)
No, no, my local tree tells me that *I* made that tag by hand and failed
to count properly... sorry for the noise!
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux•ibm.com IBM Australia Limited
next prev parent reply other threads:[~2021-02-25 22:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:34 linux-next: Fixes tag needs some work in the jc_docs tree Stephen Rothwell
2021-02-25 21:39 ` Jonathan Corbet
2021-02-25 22:01 ` Stephen Rothwell
2021-02-25 22:35 ` Andrew Donnellan [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-03 23:46 Stephen Rothwell
2023-07-04 14:32 ` Jonathan Corbet
2023-07-03 21:54 Stephen Rothwell
2022-03-28 20:58 Stephen Rothwell
2022-01-06 23:36 Stephen Rothwell
2022-01-07 10:25 ` James Clark
2022-01-07 16:19 ` Randy Dunlap
2022-01-10 10:30 ` James Clark
2022-01-07 16:35 ` Jonathan Corbet
2021-01-21 20:57 Stephen Rothwell
2019-05-20 21:44 Stephen Rothwell
2019-05-20 21:54 ` Jonathan Corbet
2019-05-21 7:18 ` Sven Eckelmann
2019-05-21 15:31 ` Jonathan Corbet
2019-05-21 18:23 ` Sven Eckelmann
2019-05-21 18:46 ` Jonathan Corbet
2019-05-21 18:52 ` Sven Eckelmann
2019-05-21 19:04 ` Jonathan Corbet
2019-05-21 19:05 ` Sven Eckelmann
2019-05-21 7:12 ` Sven Eckelmann
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=89ce7fd6-f71c-b9b2-febd-bbfafdd7b484@linux.ibm.com \
--to=ajd@linux$(echo .)ibm.com \
--cc=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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