From: "Yi Li" <lovelylich@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: [Q] Which tree should we work agains?
Date: Tue, 10 Jun 2014 06:50:45 +0000 [thread overview]
Message-ID: <006601cf8478$52fb3310$f8f19930$@gmail.com> (raw)
Hi Dan,
I’m a kernel newbie, and sorry for bother you in advanced.
From your this email: http://article.gmane.org/gmane.linux.kernel.janitors/30739,
you have pointed out we should work against linux-next tree. is it true for all of us?
From this site: https://code.google.com/p/kernel-janitors/, I got this statements:
"Q: What version should I be patching against?
A: Latest "linus" (2.6.x-rcY from kernel.org). Be sure to check -mm and -kj trees to see
if someone already did that. "
For -mm tree, is it means the linux-mm tree? after reading this wiki: http://en.wikipedia.org/wiki/Mm_tree,
it seems linux-next is the substitution for linux-mm tree's "new features" functionality.
For the -kj tree, I event can't find it from https://git.kernel.org/cgit website, only found it at here: http://cba.si/kj/
is it outdated, and un-useful?
So, in one word, could you kindly point me out which tree I should work against ?Or just kindly give me the links for document.
Thanks for your help in advanced.
regards,
Yi
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-06-10 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 6:50 Yi Li [this message]
2014-06-10 8:06 ` [Q] Which tree should we work agains? Dan Carpenter
2014-06-10 11:16 ` Dan Carpenter
2014-06-10 12:22 ` Sima Baymani
2014-06-10 17:39 ` Yi Li
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='006601cf8478$52fb3310$f8f19930$@gmail.com' \
--to=lovelylich@gmail.com \
--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.