From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: failure to fetch the cpufreq tree
Date: Mon, 21 Nov 2011 19:23:22 -0500 [thread overview]
Message-ID: <20111122002322.GA5740@redhat.com> (raw)
In-Reply-To: <20111122105756.08df5d9306102fc31e33dec7@canb.auug.org.au>
On Tue, Nov 22, 2011 at 10:57:56AM +1100, Stephen Rothwell wrote:
> Hi Dave,
>
> Fetching the cpufreq tree produces this error:
>
> fatal: Couldn't find remote ref refs/heads/next
Yeah, I've got nothing queued up for 3.3 yet.
I can push out an empty branch for you if that appeases your scripts ?
Dave
next prev parent reply other threads:[~2011-11-22 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 23:57 linux-next: failure to fetch the cpufreq tree Stephen Rothwell
2011-11-22 0:23 ` Dave Jones [this message]
2011-11-22 2:10 ` 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=20111122002322.GA5740@redhat.com \
--to=davej@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox