All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: failing to fetch the sysctl tree
Date: Sun, 06 Nov 2011 15:41:50 -0800	[thread overview]
Message-ID: <m139e0q0n5.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20111107095835.208466a386fbcf046c512d70@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 7 Nov 2011 09:58:35 +1100")

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Eric,
>
> Fetching the sysctl tree produces this error:
>
> fatal: Couldn't find remote ref refs/heads/master
>
> And indeed the sysctl tree on git.kernel.org is completely empty (i.e.
> there are no commits).  Maybe you should remove it and recreate it as a
> fork of Linus' tree.

Something weird happened when I re-uploaded things.  Apparently hitting
Ctrl-C if when you are uploading and realized you forgot to clone from
Linus's repository is fatal to how git.kernel.org manages things.  Last
I checked I could not even delete the broken repository.

Can you please switch to linux/kernel/git/ebiederm/sysctl.git instead of
sysctl-2.6.git.

With a little luck I will have something interesting in there this
round.

Thanks,
Eric

  reply	other threads:[~2011-11-06 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06 22:58 linux-next: failing to fetch the sysctl tree Stephen Rothwell
2011-11-06 23:41 ` Eric W. Biederman [this message]
2011-11-07 10:33   ` Stephen Rothwell
2011-11-07 10:33     ` Stephen Rothwell
2011-11-08  0:52     ` Eric W. Biederman

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=m139e0q0n5.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.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.