From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] KEYS: Fixes
Date: Fri, 10 Feb 2017 12:05:19 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1702101204270.3615@namei.org> (raw)
In-Reply-To: <16434.1486684538@warthog.procyon.org.uk>
On Thu, 9 Feb 2017, David Howells wrote:
> James Morris <jmorris@namei.org> wrote:
>
> > > Tagged thusly:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> > > keys-fixes-20170209
> >
> > I'm getting this:
> >
> > $ git pull
> > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git keys-fixes-20170209
> > fatal: Couldn't find remote ref keys-fixes-20170209
>
> Ummm... I can see it in the web interface for the branch:
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes
>
> and the tag itself:
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/tag/?h=keys-fixes-20170209
It works for me on a different vm with a newer version of git, which may
be the issue (I'm using 1.7.1).
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2017-02-10 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 17:17 [PATCH 0/3] KEYS: Fixes David Howells
2017-02-09 17:17 ` [PATCH 1/3] sign-file: fix build error in sign-file.c with libressl David Howells
2017-02-09 17:17 ` [PATCH 2/3] KEYS: Fix an error code in request_master_key() David Howells
2017-02-09 17:18 ` [PATCH 3/3] KEYS: Use memzero_explicit() for secret data David Howells
2017-02-09 23:07 ` [PATCH 0/3] KEYS: Fixes James Morris
2017-02-09 23:55 ` David Howells
2017-02-10 1:05 ` James Morris [this message]
2017-02-10 8:45 ` David Howells
2017-02-10 1:07 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2017-04-19 16:11 David Howells
2017-04-19 16:08 David Howells
2017-04-19 16:10 ` David Howells
2016-10-26 14:01 David Howells
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=alpine.LRH.2.20.1702101204270.3615@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--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.