All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Drebes <lists-receive@programmierforen.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [HOWTO]using git to make a local clone?
Date: Sat, 09 Jun 2007 10:19:33 +0000	[thread overview]
Message-ID: <200706091219.34352.lists-receive@programmierforen.de> (raw)
In-Reply-To: <a901b49a0706090243s275d1f62o6bfd751c3c1fcdab@mail.gmail.com>

> How can i use git to make a clone of a local kernel src tree?
> e.g i want base repo to be my downloaded vanilla kernel 2.6.18.
> How can i use git to make this as master, i clone the 2.6.18 src from
> my disk to my working directory , modify the kernel ,ass files etc and
> then merge with the 2.6.18 src base master which i downloaded.
> 
> I am facing trouble fixing this.
> All tutorials ask to pull from Linus's latest src tree which i dont
> need right now.
If you don't need the latest version of the kernel, it doesn't mean that
you don't need Linus' git repo. If you want a specific version of the kernel,
do the following:

1. Clone Linus' git repo (if not already done):
    $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

2. cd to the directoy linux-2.6

3. Every release of the kernel is tagged in the git repo. If you run
    $ git tag -l
    v2.6.11
    v2.6.11-tree
    ....
    v2.6.21
    v2.6.21-rc1
    v2.6.21-rc2
    v2.6.21-rc3
    v2.6.21-rc4
    v2.6.21-rc5
    v2.6.21-rc6
    v2.6.21-rc7
    v2.6.22-rc1
    v2.6.22-rc2
    v2.6.22-rc3
    v2.6.22-rc4
    Then you se all the tags in the current branch. As you've just
    cloned Linus' repo, you will see all the kernel releases. The releases'
    tags are prefix with the character 'v'.

4. Now you want to get the 2.6.18 stable release. You also want to have
    a new branch for you. To do both in a single step, run
    $ git branch mybranch v2.6.18

5. Finally, you want to checkout your new branch to work in it.
    $ git checkout mybranch

And there you are. You have the 2.6.18 vanilla kernel in a repo.
I hope I got you right.

Cheers,
	Andi
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2007-06-09 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-09  9:55 [KJ] [HOWTO]using git to make a local clone? psr
2007-06-09 10:19 ` Andi Drebes [this message]
2007-06-09 11:40 ` psr
2007-06-09 11:47 ` psr
2007-06-09 12:07 ` psr
2007-06-09 12:18 ` Andi Drebes
2007-06-09 12:51 ` Rene Herman
2007-06-09 13:01 ` Rene Herman
2007-06-09 13:58 ` psr

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=200706091219.34352.lists-receive@programmierforen.de \
    --to=lists-receive@programmierforen.de \
    --cc=kernel-janitors@vger.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 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.