From: "Benjamin Coddington" <bcodding@redhat.com>
To: "Trond Myklebust" <trondmy@hammerspace.com>
Cc: anna.schumaker@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Always return the error that truncates a flushing page
Date: Wed, 30 Jan 2019 09:03:25 +0000 [thread overview]
Message-ID: <78609F05-A4E4-4C6C-98A4-BF65F6E9161C@redhat.com> (raw)
In-Reply-To: <3B6A83BD-9BCB-41CD-9624-AB1158A5CB24@redhat.com>
On 29 Jan 2019, at 22:34, Benjamin Coddington wrote:
> You're right. I did
>
> # git describe c373fff7bd25
> v4.11-rc7-70-gc373fff7bd25
>
> .. and assumed it ended up in v4.11. I wonder what actually happened to
> it, I'll see if I can find out.
git describe is giving me the closest ancestor of the commit, not (what I
expected) the closest ancestor after the merge. I should use git describe
--contains instead.
Ben
prev parent reply other threads:[~2019-01-30 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 15:19 [PATCH] NFS: Always return the error that truncates a flushing page Benjamin Coddington
2019-01-28 17:59 ` Trond Myklebust
2019-01-28 18:55 ` Benjamin Coddington
2019-01-29 20:49 ` Trond Myklebust
2019-01-29 22:34 ` Benjamin Coddington
2019-01-30 9:03 ` Benjamin Coddington [this message]
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=78609F05-A4E4-4C6C-98A4-BF65F6E9161C@redhat.com \
--to=bcodding@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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).