From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nfsd tree
Date: Mon, 29 Jun 2020 14:53:59 -0400 [thread overview]
Message-ID: <20200629185359.GC2056@fieldses.org> (raw)
In-Reply-To: <20200627090317.48bf2578@canb.auug.org.au>
On Sat, Jun 27, 2020 at 09:03:17AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 886c4fe8bdff ("nfsd4: fix nfsdfs reference count loop")
>
> Fixes tag
>
> Fixes: 2c830dd720 ("nfsd: persist nfsd filesystem across mounts")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
OK, should be fixed.--b.
> 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").
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2020-06-29 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 23:03 linux-next: Fixes tag needs some work in the nfsd tree Stephen Rothwell
2020-06-29 18:53 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-03 21:40 Stephen Rothwell
2019-07-03 21:56 ` J. Bruce Fields
2019-04-08 21:43 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=20200629185359.GC2056@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).