From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
LKML <linux-kernel@vger.kernel.org>,
oprofile-list@lists.sf.net, linux-net-drivers@solarflare.com,
S390 <linux-s390@vger.kernel.org>,
linux390@de.ibm.com, virtualization@lists.osdl.org
Subject: Re: [PULL]: tip/cpus4096 updates
Date: Sun, 11 Jan 2009 03:53:40 +0100 [thread overview]
Message-ID: <20090111025340.GE7077@elte.hu> (raw)
In-Reply-To: <4966CFD9.4040602@sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/travis/linux-2.6-cpus4096-for-ingo.git
> master
hm, when i tried to pull it, i got:
fatal: Couldn't find remote ref master
Ingo
next prev parent reply other threads:[~2009-01-11 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 4:17 [PULL]: tip/cpus4096 updates Mike Travis
2009-01-11 2:53 ` Ingo Molnar [this message]
2009-01-11 2:55 ` Mike Travis
2009-01-11 2:57 ` Ingo Molnar
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=20090111025340.GE7077@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=oprofile-list@lists.sf.net \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.com \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).