From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Ts'o <tytso@mit•edu>
Cc: Zhang Yi <yi.zhang@huawei•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tag needs some work in the ext4 tree
Date: Mon, 12 Apr 2021 08:21:06 +1000 [thread overview]
Message-ID: <20210412082106.488f6642@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Hi all,
In commit
a149d2a5cabb ("ext4: fix check to prevent false positive report of incorrect used inodes")
Fixes tag
Fixes: 50122847007 ("ext4: fix check to prevent initializing reserved inodes")
has these problem(s):
- SHA1 should be at least 12 digits long
This is probably not worth rebasing to fix, but can be avoided in future
commits 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").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-04-11 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 22:21 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-03 6:44 linux-next: Fixes tag needs some work in the ext4 tree Stephen Rothwell
2023-10-08 21:21 Stephen Rothwell
2023-07-13 22:43 Stephen Rothwell
2023-07-14 8:59 ` Ojaswin Mujoo
2022-03-13 11:22 Stephen Rothwell
2021-03-21 21:11 Stephen Rothwell
2020-10-20 20:28 Stephen Rothwell
2020-09-29 9:54 Stephen Rothwell
2020-06-12 4:08 Stephen Rothwell
2019-04-25 21:03 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=20210412082106.488f6642@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tytso@mit$(echo .)edu \
--cc=yi.zhang@huawei$(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