From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] KEYS: Fixes
Date: Thu, 24 Nov 2016 23:39:51 +0000 [thread overview]
Message-ID: <5974.1480030791@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.20.1611251027140.11330@namei.org>
James Morris <jmorris@namei.org> wrote:
> $ git pull
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git keys-fixes-20161124-3
> fatal: Couldn't find remote ref keys-fixes-20161124-3
Ummm... Weird. I can see the tag through the web interface:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/tag/?h=keys-fixes-20161124-3
and it appears on the branch there:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes
David
next prev parent reply other threads:[~2016-11-24 23:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 8:51 [PATCH 0/2] KEYS: Fixes David Howells
2016-11-24 8:51 ` [PATCH 1/2] X.509: Fix double free in x509_cert_parse() David Howells
2016-11-24 8:51 ` [PATCH 2/2] MPI: Fix mpi_powm() when exponent is 0 and the result has no limbs David Howells
2016-11-24 11:20 ` Andrey Ryabinin
2016-11-24 11:35 ` David Howells
2016-11-24 12:20 ` Andrey Ryabinin
2016-11-24 11:17 ` David Howells
2016-11-24 11:22 ` Andrey Ryabinin
2016-11-24 11:33 ` David Howells
2016-11-24 12:20 ` Andrey Ryabinin
2016-11-24 12:56 ` David Howells
2016-11-24 12:57 ` David Howells
2016-11-24 13:00 ` Andrey Ryabinin
2016-11-24 22:44 ` [PATCH 0/2] KEYS: Fixes James Morris
2016-11-24 23:16 ` David Howells
2016-11-24 23:27 ` James Morris
2016-11-24 23:39 ` David Howells [this message]
2016-11-25 1:33 ` James Morris
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=5974.1480030791@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.