From: Borislav Petkov <borislav.petkov@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: fetch of edac-amd tree failed
Date: Wed, 10 Mar 2010 14:10:30 +0100 [thread overview]
Message-ID: <20100310131030.GB10679@aftab> (raw)
In-Reply-To: <20100310095013.2766db19.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, Mar 10, 2010 at 09:50:13AM +1100
> Hi Borislav,
>
> The linux-next fetch of the edac-amd tree has been failing like this for
> a few days:
>
> fatal: Couldn't find remote ref refs/heads/for-next
>
> I am still using the version from next-20100212 (which has been merged
> into Linus' tree).
Hi Stephen,
sorry about that. It should be fixed now, thanks.
--
Regards/Gruss,
Boris.
--
Advanced Micro Devices, Inc.
Operating Systems Research Center
prev parent reply other threads:[~2010-03-10 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 22:50 linux-next: fetch of edac-amd tree failed Stephen Rothwell
2010-03-10 13:10 ` Borislav Petkov [this message]
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=20100310131030.GB10679@aftab \
--to=borislav.petkov@amd.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