From: ybalrid@ybalrid.info (Arthur Brainville (Ybalrid))
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
Date: Wed, 12 Apr 2017 23:25:06 +0200 [thread overview]
Message-ID: <20170412212506.GA1223@Leliel> (raw)
In-Reply-To: <30355.1492030065@turing-police.cc.vt.edu>
On Wed, Apr 12, 2017 at 04:47:45PM -0400, valdis.kletnieks at vt.edu wrote:
> On Wed, 12 Apr 2017 20:25:11 +0200, "Arthur Brainville (Ybalrid)" said:
>
> > So, the best "branch" of developement to test if it doesn't break our
> > system is the linux-next branch, or the mainline kernel (currently
> > tagged by Linus as 4.11-RC6) ?
>
> Depends how brave you are. Linus is currently at -rc6, and linux-next
> *should* be what will become 4.12. (Should be, as in "4.11 is at -rc5, so
> people *should* already have sent maintainers patches for the next release").
>
> > I'm currently trying to understand how kernel developement is actually
> > organized, here's what I've understood
>
> You're a bit off...
>
> > So, how "linux-next" works ? Is that a "testing ground" for new kernel
> > patches? When/how does the changes the maintainers accepted are merged into
> > the mainline kernel? ^^"
>
> And explaining how you're off answers this question as well... :)
>
> Here's how it works..
>
> Developers create patches. See Documentation/process/submitting-patches.rst
> for the details on that.
>
> They then e-mail those to maintainers. See MAINTAINERS for the canonical
> list.
>
> Maintainers then review the patches, and if there's an issue, e-mail back
> to the submitter with an explanation of the issue. If the patch is OK,
> the maintainer puts it into his git tree (usually with 'git am').
>
> There may be several levels of sub-maintainer. For instance, somebody may
> maintain a driver for one specific USB sound card. They feed those patches
> to the USB sound maintainer, who then feeds it to the USB subsystem maintainer.
> That gets done by the higher-up maintainer doing a 'git pull' of the appropriate
> tree.
>
> In addition, most of the trees *also* get pulled every day and built into
> 'linux-next', to find merge conflicts and provide a test kernel.
>
> So at this point, we have top-level maintainers with trees full of patches.
>
> At some point, Linus tags the final V4.11. This opens the "merge window".
> For 2 weeks, Linus does 'git pull' from all the maintainers and merges it
> to his tree, and then tags V4.12-rc1, which closes the merge window. During
> the merge window, most maintainers will not accept new patches, because there's
> a chance that a patch could come in and be immediately merged upstream without
> having appeared in several linux-next dailys - so no testing. Once the
> window is closed, maintainers start collecting patches for the v4.13 cycle,
> and only sending Linus bugfixes and minor stuff between 4.12-rc1 and final 4.12
>
> Lather, rinse, repeat. release, merge cycle, -rc1, collect patches for next
> release, -rc8 (or so) and another release....
>
> > Oh, and, I almost forgot : If I try to use a linux-next kenrel, and
> > things breaks, who do I tell? ^^"
>
> Depends how granular you can identify the issue. If you do a 'git bisect'
> of a problem, you can narrow it down to a specific patch, you mail the patch
> author, the maintainer, any subsystem-specific list, and the linux-kernel list.
> If you just know "USB is hosed", you send it to the USB list and linux-kernel,
> and if you have *no* idea, toss it to linux-kernel.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Thanks for the explaination!
Indeed I was quite a bit off, now I know the process better ;-)
Regards,
Arthur Brainville
next prev parent reply other threads:[~2017-04-12 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1491926402.21113.kernelnewbies@kernelnewbies.org>
2017-04-12 2:30 ` Kernelnewbies Digest, Vol 77, Issue 7 Tran Ly Vu
2017-04-12 10:29 ` Nan Xiao
2017-04-12 11:32 ` Sébastien Masson
2017-04-12 12:34 ` How to contribute (was " valdis.kletnieks at vt.edu
2017-04-12 18:25 ` Arthur Brainville (Ybalrid)
2017-04-12 20:47 ` valdis.kletnieks at vt.edu
2017-04-12 21:25 ` Arthur Brainville (Ybalrid) [this message]
2017-04-16 6:31 ` Aishwarya Pant
2017-04-16 7:17 ` Amit Kumar
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=20170412212506.GA1223@Leliel \
--to=ybalrid@ybalrid.info \
--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.