All of lore.kernel.org
 help / color / mirror / Atom feed
From: j.neuschaefer@gmx.net (Jonathan Neuschäfer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: I am hoping to develop the linux kernel, which version should I modify
Date: Mon, 24 Oct 2011 02:24:50 +0200	[thread overview]
Message-ID: <20111024002450.GC2590@debian.debian> (raw)
In-Reply-To: <CAAgJb5vWfnQ9ZU-D6g5oqwv=OKMi4qbfNBTzAgT8C5pVtAcv4Q@mail.gmail.com>

On Mon, Oct 24, 2011 at 08:08:31AM +0800, Jimmy Pan wrote:
> There is a 3.0 in my hard disk, which I downloaded around Aug 10. There is
> 3.0.4 and 3.1-rc4 code. Which version should I use. Since I am a newbie, I
> think I don't need to use the newest version. Can I use my 3.0 version, or
> should I download a new one?

A lot of people use Git[0] to download and manage their kernel source
code, but you can also use the latest mainline (2.6.39, 3.0, ...) or
-rc release, if you like.

To get the kernel source via git, run this (it'll take a while, because
it downloads around 200 megabytes):

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

> Maybe I can read the kernel source on the web, is there a way to use the
> source on web to make patches?

You can read the linux source code on the web[1,2], but you sure need
it on your own computer, if you're going to change things.

> Thanks in advance.

Well, thanks for this polite and informed post. :-)

[0] http://git-scm.com/
[1] http://lxr.linux.no/linux
[2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=tree


Greetings,
	Jonathan Neusch?fer

  reply	other threads:[~2011-10-24  0:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  0:08 I am hoping to develop the linux kernel, which version should I modify Jimmy Pan
2011-10-24  0:24 ` Jonathan Neuschäfer [this message]
2011-10-24  0:29   ` Jonathan Neuschäfer

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=20111024002450.GC2590@debian.debian \
    --to=j.neuschaefer@gmx.net \
    --cc=kernelnewbies@lists.kernelnewbies.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.