From: Erik Mouw <erik@harddisk-recovery.com>
To: Walkinair <walktodeath@163.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to get kernel source release from git tree?
Date: Tue, 20 Jun 2006 18:16:21 +0200 [thread overview]
Message-ID: <20060620161620.GA4487@harddisk-recovery.com> (raw)
In-Reply-To: <4497830B.5010402@163.com>
On Tue, Jun 20, 2006 at 01:09:31PM +0800, Walkinair wrote:
> Hi, this may be a stupid question, sorry for this.
>
> I have kenel 2.6 git tree in my local box, usually through the following
> steps I get source release,
> 1. copy git repository to a new directory.
> 2. rm .git directory.
> 3. make config; make; make modules_install; make install
>
> I there any convinient git command or other ways to get kernel release
> from git repository?
What about this?
git tar-tree v2.6.17 linux-2.6.17 | ( cd .. ; tar xpf - )
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
prev parent reply other threads:[~2006-06-20 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 5:09 How to get kernel source release from git tree? Walkinair
2006-06-20 5:17 ` H. Peter Anvin
2006-06-20 5:52 ` Yao Fei Zhu
2006-06-20 16:16 ` Erik Mouw [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=20060620161620.GA4487@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=walktodeath@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.