From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-fscrypt@vger.kernel.org>
Subject: Re: [GIT PULL] fscrypt update for 4.21
Date: Sun, 6 Jan 2019 14:56:06 -0500 [thread overview]
Message-ID: <20190106195606.GA6741@mit.edu> (raw)
In-Reply-To: <20190106172005.GA699@sol.localdomain>
On Sun, Jan 06, 2019 at 09:20:07AM -0800, Eric Biggers wrote:
> Hi Ted, that tag is still on an old commit. Probably you forgot to push.
My scripts check to see that it was right (at least from my view of
git.kernel.org) before it generates the push. I just checked and it's
correct now, and I haven't done any intervening pushes. I think it
must have been a stale cache entry that you saw?
- Ted
next prev parent reply other threads:[~2019-01-06 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 13:49 [GIT PULL] fscrypt update for 4.21 Theodore Y. Ts'o
2019-01-06 17:20 ` Eric Biggers
2019-01-06 17:52 ` Eric Biggers
2019-01-06 19:56 ` Theodore Y. Ts'o [this message]
2019-01-06 21:35 ` pr-tracker-bot
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=20190106195606.GA6741@mit.edu \
--to=tytso@mit.edu \
--cc=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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