From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Cc: Zhang Xiaoxu <zhangxiaoxu5@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 cifs tree
Date: Wed, 16 Nov 2022 07:41:46 +1100 [thread overview]
Message-ID: <20221116074146.6e7cbce9@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
Hi all,
In commit
9898f0456aa3 ("cifs: Fix wrong return value checking when GETFLAGS")
Fixes tag
Fixes: 64a5cfa6db9 ("Allow setting per-file compression via SMB2/3")
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").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-11-15 20:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 20:41 Stephen Rothwell [this message]
2022-11-16 6:22 ` linux-next: Fixes tag needs some work in the cifs tree Steve French
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 21:09 Stephen Rothwell
2023-02-23 21:27 ` David Howells
2023-02-23 22:43 ` Steve French
2022-10-15 8:57 Stephen Rothwell
2022-10-15 15:06 ` Steve French
2022-10-05 23:30 Stephen Rothwell
2022-10-06 2:18 ` Steve French
2022-08-30 21:42 Stephen Rothwell
2022-08-30 22:10 ` Steve French
2022-08-24 6:37 Stephen Rothwell
2022-08-24 14:23 ` Steve French
2022-07-05 22:06 Stephen Rothwell
2021-05-19 21:53 Stephen Rothwell
2021-05-20 0:21 ` Steve French
2019-05-24 4:27 Stephen Rothwell
2019-05-24 14:14 ` Steve French
2019-05-29 3:24 ` Murphy Zhou
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=20221116074146.6e7cbce9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=zhangxiaoxu5@huawei.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).