From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dean Nelson <dnelson@redhat.com>, Russ Anderson <rja@sgi.com>,
ozan@pardus.org.tr, Jaswinder Singh Rajput <jaswinder@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Yinghai Lu <yinghai@kernel.org>,
Gene Heskett <gene.heskett@verizon.net>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Mark Hounschell <markh@compro.net>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
David Rientjes <rientjes@google.com>,
Haicheng Li <haicheng.li@linux.intel.com>
Subject: Re: [GIT PULL] x86 fixes for 2.6.33-rc6
Date: Wed, 27 Jan 2010 08:26:08 -0800 [thread overview]
Message-ID: <4B606920.8000306@zytor.com> (raw)
In-Reply-To: <20100127112446.GA19613@elte.hu>
On 01/27/2010 03:24 AM, Ingo Molnar wrote:
>
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>> On Wed, 27 Jan 2010, H. Peter Anvin wrote:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/x86/linux-2.6-tip.git x86-fixes-for-linus
>>
>> That doesn't work for me at all.
>
> i think Peter typoed it and the git/ portion went missing, it should have
> been:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git x86-fixes-for-linus
>
>> I assume you meant
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-fixes-for-linus
>>
>> (note the "git/tip" instead of "x86")
>
> Yes, that works too. The x86 repo is symlinked to the tip repo.
>
Sorry about that. Get it done before bed syndrome.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2010-01-27 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 8:33 [GIT PULL] x86 fixes for 2.6.33-rc6 H. Peter Anvin
2010-01-27 10:50 ` Linus Torvalds
2010-01-27 11:24 ` Ingo Molnar
2010-01-27 16:26 ` H. Peter Anvin [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=4B606920.8000306@zytor.com \
--to=hpa@zytor.com \
--cc=andreas.herrmann3@amd.com \
--cc=dnelson@redhat.com \
--cc=gene.heskett@verizon.net \
--cc=haicheng.li@linux.intel.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=mingo@elte.hu \
--cc=ozan@pardus.org.tr \
--cc=rientjes@google.com \
--cc=rja@sgi.com \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=yinghai@kernel.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