From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 2/9] Documentation/development-process: add maintainers and git info
Date: Sun, 23 May 2010 17:02:30 -0700 [thread overview]
Message-ID: <1274659350528@xenotime.net> (raw)
In-Reply-To: <12746593501290@xenotime.net>
From: Randy Dunlap <randy.dunlap@oracle.com>
Add info on maintainers and persistent posting.
Update git home page.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Acked-by: Jonathan Corbet <corbet@lwn.net>
---
Documentation/development-process/2.Process | 15 ++++++++---
Documentation/development-process/7.AdvancedTopics | 2 -
2 files changed, 13 insertions(+), 4 deletions(-)
--- lnx-2634-docs.orig/Documentation/development-process/2.Process
+++ lnx-2634-docs/Documentation/development-process/2.Process
@@ -151,7 +151,7 @@ The stages that a patch goes through are
well.
- Wider review. When the patch is getting close to ready for mainline
- inclusion, it will be accepted by a relevant subsystem maintainer -
+ inclusion, it should be accepted by a relevant subsystem maintainer -
though this acceptance is not a guarantee that the patch will make it
all the way to the mainline. The patch will show up in the maintainer's
subsystem tree and into the staging trees (described below). When the
@@ -159,6 +159,15 @@ The stages that a patch goes through are
the discovery of any problems resulting from the integration of this
patch with work being done by others.
+- Please note that most maintainers also have day jobs, so merging
+ your patch may not be their highest priority. If your patch is
+ getting feedback about changes that are needed, you should either
+ make those changes or justify why they should not be made. If your
+ patch has no review complaints but is not being merged by its
+ appropriate subsystem or driver maintainer, you should be persistent
+ in updating the patch to the current kernel so that it applies cleanly
+ and keep sending it for review and merging.
+
- Merging into the mainline. Eventually, a successful patch will be
merged into the mainline repository managed by Linus Torvalds. More
comments and/or problems may surface at this time; it is important that
@@ -319,9 +328,9 @@ developers; even if they do not use it f
to keep up with what other developers (and the mainline) are doing.
Git is now packaged by almost all Linux distributions. There is a home
-page at
+page at:
- http://git.or.cz/
+ http://git-scm.com/
That page has pointers to documentation and tutorials. One should be
aware, in particular, of the Kernel Hacker's Guide to git, which has
--- lnx-2634-docs.orig/Documentation/development-process/7.AdvancedTopics
+++ lnx-2634-docs/Documentation/development-process/7.AdvancedTopics
@@ -25,7 +25,7 @@ long document in its own right. Instead
fits into the kernel development process in particular. Developers who
wish to come up to speed with git will find more information at:
- http://git.or.cz/
+ http://git-scm.com/
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
--
next prev parent reply other threads:[~2010-05-24 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 0:02 [PATCH 1/9] docbook: make mtd nand module init static Randy Dunlap
2010-05-24 0:02 ` [PATCH 9/9] Documentation: update SubmitChecklist for O=objdir and kconfig testing Randy Dunlap
2010-05-24 0:02 ` Randy Dunlap [this message]
2010-05-24 0:02 ` [PATCH 5/9] Documentation/vm: use better value for MAP_HUGETLB Randy Dunlap
2010-05-24 0:02 ` [PATCH 4/9] Documentation/timers/hpet_example: drop duplicate header files Randy Dunlap
2010-05-24 0:02 ` [PATCH 7/9] scsi_scan.c: fix/convert functions to use kernel-doc Randy Dunlap
2010-05-24 0:02 ` [PATCH 3/9] Documentation/development-process: add staging & mmotm info Randy Dunlap
2010-05-24 0:02 ` [PATCH 6/9] scsi: update torque.net references to current location Randy Dunlap
2010-05-24 0:02 ` [PATCH 8/9] fusion: fix kernel-doc notation Randy Dunlap
2010-05-24 0:10 ` [PATCH 1/9] docbook: make mtd nand module init static Randy Dunlap
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=1274659350528@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=corbet@lwn.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).