<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div>Thanks for doing that!<br><br></div>I'm afraid I cannot be very specific, but one thing I've noticed in general is that there is not a great deal of easy-to-google and yet accurate information on linux-next or the mm tree. Because kernelnewbies is a well known site, information there might help folks who google for this info.<br>
<br></div>I edited the wikipedia article on the mm tree a little bit to clear up some of the most inaccurate stuff after learning about the mm tree via hard knocks and email exchanges with Andrew Morton. I learned bunches about linux-next but haven't been able to put the information anywhere, since it's spread on obsolete blog entries and such.<br>
</div>
<br></div>Newbies to kernel development might be interested in the mm tree because it has a lot of new features, fixes, and experimental things. If you don't need to have the mm tree of *right now*, there's even a branch in linux-next, which you can use in git as "linux-next/akpm" once you add the linux-next remote.<br>
<br></div><div>Newbies will be interested in linux-next because that's where the subsystem maintainers are trying to get their work to apply, so a newbie would probably want their work to apply there too, or at least to know about problems if it doesn't apply cleanly.<br>
</div><div><br></div><div>I bet staging is pretty well covered already.<br></div><div><br></div>I think the reason nobody has updated the info on linux-next is that it's so easy to use once you add the remote repo to your git tree. You might add and use it like this:<br>
<br></div>git remote add linux-next git://<a href="http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git" target="_blank">git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git</a><br></div>git fetch linux-next<br>
</div>
git checkout linux-next/akpm<br></div>git branch newbiestuff<br></div>vi net/core/dev.c # or whatever<br></div>git commit -a -m 'net: changed something or whatevs'<br></div>git format-patch -o /tmp/newbiepatches \<br>
-s \<br> --to="<a href="mailto:someone@example.com" target="_blank">someone@example.com</a>" \<br> --cc="<a href="mailto:someoneelse@example.com" target="_blank">someoneelse@example.com</a>" \<br>
--cover-letter \<br> --numbered-files \<br>
--thread=shallow \<br> linux-next/akpm<br></div>vi /tmp/newbiepatches/0 # mention the upstream commit by hash and name in cover letter<br><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Dec 21, 2012 at 9:48 AM, leam hall <span dir="ltr"><<a href="mailto:leamhall@gmail.com" target="_blank">leamhall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br><br>Being a rampant instigator I've managed to get page edit rights to <a href="http://kernelnewbies.org/" target="_blank">http://kernelnewbies.org/</a>. If you see anything that can be improved, let me know. I don't own or control the site but am trying to add information and remove dead links.<span class="HOEnZb"><font color="#888888"><br>
<br>Leam<br clear="all"><br>-- <br><div><a href="http://leamhall.blogspot.com/" target="_blank">Mind on a Mission</a></div>
</font></span><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br> Ed Cashin <<a href="mailto:ecashin@noserose.net">ecashin@noserose.net</a>><br> <a href="http://noserose.net/e/">http://noserose.net/e/</a><br> <a href="http://www.coraid.com/">http://www.coraid.com/</a>
</div>