From: Russell King <rmk@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: unable to fetch the arm tree
Date: Mon, 14 Nov 2016 10:22:19 +0000 [thread overview]
Message-ID: <20161114102219.GE17314@flint.armlinux.org.uk> (raw)
In-Reply-To: <20161114092922.2963d6d8@canb.auug.org.au>
On Mon, Nov 14, 2016 at 09:29:22AM +1100, Stephen Rothwell wrote:
> Hi Russell,
>
> I could not fetch the arm or arm-current trees
> (git://git.armlinux.org.uk/~rmk/linux-arm.git) this morning:
>
> fatal: remote error: access denied or repository not exported: ~rmk/linux-arm.git
>
> I will use the previous versions that I have.
Gah, that's down to selinux having an argument over how the repository
should be labelled - different parts of the system want different
labels on that. selinux is sometimes a nightmare.
Should be fixed now.
--
Russell King
ARM architecture Linux Kernel maintainer
next prev parent reply other threads:[~2016-11-14 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:29 linux-next: unable to fetch the arm tree Stephen Rothwell
2016-11-14 10:22 ` Russell King [this message]
2016-11-14 10:42 ` 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=20161114102219.GE17314@flint.armlinux.org.uk \
--to=rmk@armlinux.org.uk \
--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.