From: Andi Kleen <ak@linux.intel.com>
To: Ryan Wang <openspace.wang@gmail.com>
Cc: cpw@sgi.com, linux-numa@vger.kernel.org
Subject: Re: Where can I get the git tree for linux numa userland tool?
Date: Sun, 1 Jan 2012 22:31:30 -0800 [thread overview]
Message-ID: <20120102063130.GA2965@alboin.amr.corp.intel.com> (raw)
In-Reply-To: <CAPxxNQnpEyzexU26iQNQgXG8m8COekL1yrme4y21dB0z3m+weg@mail.gmail.com>
On Thu, Dec 29, 2011 at 12:46:07PM +0800, Ryan Wang wrote:
> Sorry to trouble you!
>
> I'm new to linux numa, and I want to reach the git tree
> for the latest code.
>
> Will you please give me some hits?
numactl is currently not maintained in a official git tree
(I tend to keep a private one for my patches),
but maintained old style with patches only.
The releases and RCs can be downloaded from
http://oss.sgi.com/projects/libnuma/
As for having a git tree: I think it would be a good idea,
but it would be Cliff's choice as he is the maintainer.
-Andi
parent reply other threads:[~2012-01-02 6:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAPxxNQnpEyzexU26iQNQgXG8m8COekL1yrme4y21dB0z3m+weg@mail.gmail.com>]
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=20120102063130.GA2965@alboin.amr.corp.intel.com \
--to=ak@linux.intel.com \
--cc=cpw@sgi.com \
--cc=linux-numa@vger.kernel.org \
--cc=openspace.wang@gmail.com \
/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).