public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Tony Luck <tony.luck@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [GIT PATCH] APEI patches for Linux 3.1
Date: Wed, 3 Aug 2011 13:02:53 -0700	[thread overview]
Message-ID: <20110803130253.db8dd045.rdunlap@xenotime.net> (raw)
In-Reply-To: <CA+8MBbKavpgkf-ByB5-x9k5NCnW_W9Nkp2pQMXTGvTZEdTYg1w@mail.gmail.com>

On Wed, 3 Aug 2011 12:10:14 -0700 Tony Luck wrote:

> On Wed, Aug 3, 2011 at 9:26 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >  fatal: Couldn't find remote ref apei-release
> >
> > Forgot yo push?
> 
> Looks like he pushed to the wrong tree. There is a 3 hour old
> apei-release branch here:
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-idle-2.6.git
> apei-release

Len did send a follow-up (correction) email that said:

typo fixed -- the real tree is here

git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git apei-release


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-08-03 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 15:39 [GIT PATCH] APEI patches for Linux 3.1 Len Brown
2011-08-03 15:42 ` Len Brown
2011-08-03 16:26 ` Linus Torvalds
2011-08-03 19:10   ` Tony Luck
2011-08-03 20:02     ` Randy Dunlap [this message]
2011-08-03 19:26   ` Len Brown
2011-08-04  0:52     ` Linus Torvalds
2011-08-04  1:10       ` huang ying
2011-08-04  1:34         ` Stephen Rothwell
2011-08-04  4:25       ` Len Brown

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=20110803130253.db8dd045.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    /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