From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Getting started.
Date: Sun, 29 May 2005 21:48:19 +0000 [thread overview]
Message-ID: <20050529214819.GA17743@nd47.coderock.org> (raw)
In-Reply-To: <200505281647.54075.jason@jcorcoran.net>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On 28/05/05 10:41 -0700, randy_dunlap wrote:
> On Sat, 28 May 2005 16:47:53 +0100 Jason Corcoran wrote:
>
> | Ok,
> |
> | I have now got some free time, after lurking on the list for a week or so.
> | Should I be looking at rc5 or rc4 of 2.6.12, I noticed there is a patch on
> | the janitors website?
>
> (maybe the KJ maintainer would like to comment :)
>
Hmm?
>
> You should be making patches to latest "linus" (kernel.org)
> kernels, e.g., linux-2.6.12-rc5.
> However, you generally also need to check that patches for what you
> are working on have not already been made by looking at:
> - the -mm patchset
> - the -kj patchset
>
Added this to "faq":
+Q: What version should I be patching against?
+A: Latest "linus" (2.6.x-prey from kernel.org).
+ Be sure to check -mm and -kj trees to see if someone already did that.
+
> You could go even further and check the current kernel git archive
> or mailing lists that are appropriate for the area that you are
> patching, but that's probably asking too much.
>
> The current kernel git archive is viewable at:
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary
>
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-05-29 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 15:47 [KJ] Getting started Jason Corcoran
2005-05-28 17:41 ` randy_dunlap
2005-05-29 21:48 ` Domen Puncer [this message]
2005-05-29 22:24 ` Alexey Dobriyan
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=20050529214819.GA17743@nd47.coderock.org \
--to=domen@coderock.org \
--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.