* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/kernel: maintenance.xml
@ 2007-11-06 23:11 Daniel Drake (dsd)
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Drake (dsd) @ 2007-11-06 23:11 UTC (permalink / raw
To: gentoo-commits
dsd 07/11/06 23:11:34
Modified: maintenance.xml
Log:
add linux-stable documentation
Revision Changes Path
1.2 xml/htdocs/proj/en/kernel/maintenance.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?r1=1.1&r2=1.2
Index: maintenance.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- maintenance.xml 30 Apr 2007 02:10:08 -0000 1.1
+++ maintenance.xml 6 Nov 2007 23:11:34 -0000 1.2
@@ -819,15 +819,42 @@
</section>
</chapter>
+
<chapter>
<title>genpatches and linux-stable</title>
+
+<section>
+<title>Submission criteria</title>
+<body>
+
+<ul>
+<li>This section is aimed at documenting the process for Gentoo kernel developers only (rather than just prospective ones), but if you're really keen, feel free to ask on IRC if you'd like to submit a patch.</li>
+<li>The patch must conform to the stable kernel rules, see Documentation/stable_kernel_rules.txt</li>
+<li>The patch must have been shipped in at least one gentoo-sources release. The reasoning here is that some of the time, patches committed to genpatches are untested -- full testing is carried out before release.</li>
+<li>The patch must not already be in the stable queue. Check the
+<uri link="http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=tree">stable-queue.git web interface</uri>.</li>
+</ul>
+
+</body>
+</section>
+
<section>
+<title>Submission process</title>
<body>
<p>
-to be written later
+Prepare an email in the following way:
</p>
+<ul>
+<li>Addressed to stable@kernel.org</li>
+<li>CC kernel@gentoo.org</li>
+<li>CC the patch author, who's contact details can be found in the patch</li>
+<li>Use the same subject line as the one in the patch, prepended with [PATCH] if it is not there already.</li>
+<li>In the message body, include a very brief description with a reference to the Gentoo bug report, for example: This patch fixes a bootup crash in the snd-intel-hda driver as detailed at http://bugs.gentoo.org/12345</li>
+<li><e>Attach</e> the patch to the email, directly from genpatches. The patch should have come from gitweb or similar and already have the authorship details, commit ID, etc.</li>
+</ul>
+
</body>
</section>
</chapter>
--
gentoo-commits@gentoo.org mailing list
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/kernel: maintenance.xml
@ 2008-11-19 12:42 Daniel Drake (dsd)
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Drake (dsd) @ 2008-11-19 12:42 UTC (permalink / raw
To: gentoo-commits
dsd 08/11/19 12:42:45
Modified: maintenance.xml
Log:
small updates
Revision Changes Path
1.3 xml/htdocs/proj/en/kernel/maintenance.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?r1=1.2&r2=1.3
Index: maintenance.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- maintenance.xml 6 Nov 2007 23:11:34 -0000 1.2
+++ maintenance.xml 19 Nov 2008 12:42:45 -0000 1.3
@@ -17,8 +17,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.1</version>
-<date>2007-04-29</date>
+<version>0.2</version>
+<date>2008-11-19</date>
<chapter>
<title>Introduction</title>
@@ -39,6 +39,12 @@
<uri link="http://dev.gentoo.org/~dsd/genpatches/">genpatches homepage</uri>.
</p>
+<p>
+This document was written by Daniel Drake, the kernel project lead. References
+to "me" in this document refer to Daniel, but please do not feel that this is
+a one-man project. Other members of the team are happy to help you as well.
+</p>
+
</body>
</section>
</chapter>
@@ -106,8 +112,11 @@
</p>
<p>
-My username is <c>dsd_</c>. For quick one-off questions, IRC is the most
-convenient way to work with me.
+While learning, please ask us questions! This is the best way to learn. If we don't respond, ask again another time. We do want to help you, since hopefully that will result in you helping us in the future!
+</p>
+
+<p>
+The primary kernel maintainers are Daniel Drake (IRC username <c>dsd_</c>) and Mike Pagano (IRC username <c>mpagano</c>).
</p>
</body>
@@ -188,7 +197,7 @@
</p>
<pre caption="Checking out genpatches from anonymous SVN">
-# svn co http://anonsvn.gentoo.org/repositories/linux-patches/genpatches-2.6/trunk genpatches
+# svn co svn://anonsvn.gentoo.org/linux-patches/genpatches-2.6/trunk genpatches
</pre>
</body>
@@ -207,8 +216,7 @@
<li><uri link="http://bugzilla.kernel.org">Kernel bugzilla</uri></li>
<li><uri link="http://dev.gentoo.org/~dsd/genpatches">genpatches homepage</uri></li>
<li><uri link="http://www.kernel.org">kernel.org</uri></li>
-<li><uri link="http://lxr.free-electrons.com/">LXR Cross Referencer</uri> - useful if you are digging into the source code</li>
-<li><uri link="http://lxr.linux.no/source/">LXR mirror</uri> - not updated as frequently</li>
+<li><uri link="http://lxr.linux.no/">LXR Cross Referencer</uri> - useful if you are digging into the source code</li>
<li><uri link="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary">gitweb: Linus' tree</uri> - kernel releases are generated from this repository</li>
<li><uri link="http://git.kernel.org">gitweb: index of kernel repositories</uri></li>
</ul>
@@ -258,7 +266,7 @@
</p>
<p>
-Even after 2 years of bug handling, I personally am familiar with only a very
+Even after 3 years of bug handling, I personally am familiar with only a very
small proportion of the kernel codebase. It's important that we raise these
bugs to the attention of the upstream kernel developers who do know what they
are doing, and it's important that we do this quickly. As you will learn, we
@@ -680,9 +688,7 @@
If the user doesn't respond to the request to file the bug upstream, discard
the bug like you would for other unresponsive cases. Since you closed
it as UPSTREAM, it will drop off the buglist anyway -- so do remember to
-continue the process when they do respond with the upstream bug URL.
-In future, the linux-bugzilla-pending keyword should allow us to measure how
-often bugs get lost at this point (this is a recent addition to the process).
+continue the process when they do respond with the upstream bug URL. The linux-bugzilla-pending keyword allows us to measure how often bugs get lost at this point, and allows us to follow up.
</p>
<p>
@@ -738,8 +744,8 @@
<p>
I realise this is a pain, but it's only a temporary one. Once you've made
-several contributions to bugs in this form, I will request that your bugzilla
-access be raised so that you can perform these tasks on your own.
+several contributions to bugs in this form, I will increase your bugzilla
+access permissions so that you can perform these tasks on your own.
</p>
<p>
@@ -796,27 +802,30 @@
All core kernel bugs are assigned to <c>kernel@gentoo.org</c> by default. When
a bug has been solved but is not fixed in portage (i.e. is pending a patch
being added to genpatches, or pending the next genpatches/gentoo-sources
-release), it gets reassigned to the gentoo-sources maintainer, currently
-<c>dsd@gentoo.org</c>. When reassigning the bug, please add
-<c>kernel@gentoo.org</c> to the CC list.
+release), we add the InSVN bugzilla keyword.
</p>
</body>
</section>
-</chapter>
-
-<chapter>
-<title>Working with upstream development trees</title>
<section>
+<title>Bug resolution</title>
<body>
<p>
-to be written later
+When a bug has been solved but is not fixed in portage (i.e. is pending a patch
+being added to genpatches, or pending the next genpatches/gentoo-sources
+release), we add the <c>InSVN</c> bugzilla keyword.
+</p>
+
+<p>
+The bug is then closed with an appropriate message when a new kernel release
+(incorporating the fix) is added to the portage tree.
</p>
</body>
</section>
+
</chapter>
@@ -867,8 +876,28 @@
<p>
Look at some bug reports from the saved searches you configured earlier. If
you can contribute straight off, go right ahead. However, I expect you'll
-probably be unsure what should happen next. So, pick a bug, and question me
-about it, preferably on IRC in #gentoo-kernel.
+probably be unsure what should happen next. So, pick a bug, and question us
+about it, preferably on IRC in #gentoo-kernel. Alternatively, you could write
+to the gentoo-kernel mailing list.
+</p>
+
+<p>
+It may seem that many of the open bugs are already in good hands, waiting on
+the user, or something like that. However, please stick around, because we
+get a steady flow of new bugs!
+</p>
+
+<p>
+While this document has introduced you to the processes, you may not feel
+capable of jumping into problems and solving bugs. That's fine! Because you
+have put kernel@gentoo.org on your bugzilla watchlist, you will see bugs as
+they come in <e>and</e> the way that we fix them. Observe how we handle and
+solve the issues. Sooner or later, you will be able to mimick our activities
+on other bugs, and you'll be away!
+</p>
+
+<p>
+Thank you for your interest in helping us!
</p>
</body>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/kernel: maintenance.xml
@ 2008-11-25 12:37 Daniel Drake (dsd)
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Drake (dsd) @ 2008-11-25 12:37 UTC (permalink / raw
To: gentoo-commits
dsd 08/11/25 12:37:44
Modified: maintenance.xml
Log:
remove InSVN duplication and fix guide tag, thanks to Chema Alonso
Revision Changes Path
1.4 xml/htdocs/proj/en/kernel/maintenance.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?r1=1.3&r2=1.4
Index: maintenance.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- maintenance.xml 19 Nov 2008 12:42:45 -0000 1.3
+++ maintenance.xml 25 Nov 2008 12:37:44 -0000 1.4
@@ -3,7 +3,7 @@
1.16 2006/07/23 12:27:14 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<guide link="/doc/en/kernel-upgrade.xml">
+<guide link="/proj/en/kernel/maintenance.xml">
<title>Gentoo Linux Kernel Maintainers Guide</title>
<author title="Author">
<mail link="dsd@gentoo.org">Daniel Drake</mail>
@@ -795,20 +795,6 @@
</section>
<section>
-<title>Bug Assignment</title>
-<body>
-
-<p>
-All core kernel bugs are assigned to <c>kernel@gentoo.org</c> by default. When
-a bug has been solved but is not fixed in portage (i.e. is pending a patch
-being added to genpatches, or pending the next genpatches/gentoo-sources
-release), we add the InSVN bugzilla keyword.
-</p>
-
-</body>
-</section>
-
-<section>
<title>Bug resolution</title>
<body>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/kernel: maintenance.xml
@ 2010-02-19 14:00 Mike Pagano (mpagano)
0 siblings, 0 replies; 5+ messages in thread
From: Mike Pagano (mpagano) @ 2010-02-19 14:00 UTC (permalink / raw
To: gentoo-commits
mpagano 10/02/19 14:00:28
Modified: maintenance.xml
Log:
Change additional reference to genpatches to my devspace
Revision Changes Path
1.5 xml/htdocs/proj/en/kernel/maintenance.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?r1=1.4&r2=1.5
Index: maintenance.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- maintenance.xml 25 Nov 2008 12:37:44 -0000 1.4
+++ maintenance.xml 19 Feb 2010 14:00:28 -0000 1.5
@@ -36,7 +36,7 @@
designed to be minimal, Gentoo-independent, and accessible to other
distributions and projects. Please ensure you have a good
understanding of genpatches before continuing: read through the
-<uri link="http://dev.gentoo.org/~dsd/genpatches/">genpatches homepage</uri>.
+<uri link="http://dev.gentoo.org/~mpagano/genpatches/">genpatches homepage</uri>.
</p>
<p>
@@ -214,7 +214,7 @@
<ul>
<li><uri link="https://bugs.gentoo.org">Gentoo bugzilla</uri></li>
<li><uri link="http://bugzilla.kernel.org">Kernel bugzilla</uri></li>
-<li><uri link="http://dev.gentoo.org/~dsd/genpatches">genpatches homepage</uri></li>
+<li><uri link="http://dev.gentoo.org/~mpagano/genpatches">genpatches homepage</uri></li>
<li><uri link="http://www.kernel.org">kernel.org</uri></li>
<li><uri link="http://lxr.linux.no/">LXR Cross Referencer</uri> - useful if you are digging into the source code</li>
<li><uri link="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary">gitweb: Linus' tree</uri> - kernel releases are generated from this repository</li>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/kernel: maintenance.xml
@ 2012-10-28 15:21 Sven Vermeulen (swift)
0 siblings, 0 replies; 5+ messages in thread
From: Sven Vermeulen (swift) @ 2012-10-28 15:21 UTC (permalink / raw
To: gentoo-commits
swift 12/10/28 15:21:08
Modified: maintenance.xml
Log:
Removing link attribute from guides
Revision Changes Path
1.6 xml/htdocs/proj/en/kernel/maintenance.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?r1=1.5&r2=1.6
Index: maintenance.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- maintenance.xml 19 Feb 2010 14:00:28 -0000 1.5
+++ maintenance.xml 28 Oct 2012 15:21:08 -0000 1.6
@@ -3,7 +3,7 @@
1.16 2006/07/23 12:27:14 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<guide link="/proj/en/kernel/maintenance.xml">
+<guide>
<title>Gentoo Linux Kernel Maintainers Guide</title>
<author title="Author">
<mail link="dsd@gentoo.org">Daniel Drake</mail>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-10-28 15:25 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-06 23:11 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/kernel: maintenance.xml Daniel Drake (dsd)
-- strict thread matches above, loose matches on Subject: below --
2008-11-19 12:42 Daniel Drake (dsd)
2008-11-25 12:37 Daniel Drake (dsd)
2010-02-19 14:00 Mike Pagano (mpagano)
2012-10-28 15:21 Sven Vermeulen (swift)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox