From: Paul Moore <paul@paul-moore.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error when fetching the selinux tree
Date: Wed, 06 Nov 2013 17:29:14 -0500 [thread overview]
Message-ID: <1869239.Kz8bBo099V@sifl> (raw)
In-Reply-To: <20131107092709.09c9e76757362bad1f1dd885@canb.auug.org.au>
On Thursday, November 07, 2013 09:27:09 AM Stephen Rothwell wrote:
> Hi Paul,
>
> Fetching the selinux tree
> (git://git.infradead.org/users/pcmoore/selinux#master) produces this
> error:
>
> fatal: Couldn't find remote ref refs/heads/master
Sorry about that, a case of bad timing. I'm doing some cleanup right now, it
should be back up shortly. That said, it should be empty today so no worries
if you want to skip it today.
-Paul
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2013-11-06 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 22:27 linux-next: error when fetching the selinux tree Stephen Rothwell
2013-11-06 22:29 ` Paul Moore [this message]
2013-11-06 22:31 ` 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=1869239.Kz8bBo099V@sifl \
--to=paul@paul-moore.com \
--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 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.