From: Luke Yang <luke.adi@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel development process questions
Date: Wed, 21 Dec 2005 13:17:35 +0800 [thread overview]
Message-ID: <489ecd0c0512202117q303ef7f1qae6bc08c9637be39@mail.gmail.com> (raw)
Hi all,
Thanks for Greg's howto and others' documents (Such as the "kernel
hacker's guide to git). But I still have some detail questions:
Which is everyone working on: the "latest linus git tree" or the
"-mm kernel"? As I tried, the -mm kernel is only a patch, which MAY
can not be applied to latest kernel. For example, current
2.6.15-rc5-mm3 patch can't be applied to current kernel without
rejections and conflicts.
As Greg pointed out, most patches should be tested on -mm kernel.
So I assum that a developer just get an exact 2.6.15-rc5 kernel from
git, apply the 2.6.15-rc5-mm3 patch, do some work and send out the
patch, then just stay there for next -mm patch?
Thanks in advace!
BTW: git question, Is there any way to get my .git/refs/ folder
updated through http? I mean not through rsync?
Regards,
Luke Yang
Analog Device Inc.
next reply other threads:[~2005-12-21 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 5:17 Luke Yang [this message]
2005-12-21 9:17 ` Jesper Juhl
2005-12-29 11:10 ` kernel development process questions (updating git tags) Marco Roeland
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=489ecd0c0512202117q303ef7f1qae6bc08c9637be39@mail.gmail.com \
--to=luke.adi@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®