summaryrefslogtreecommitdiff
path: root/Documentation/development-process/7.AdvancedTopics
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2011-03-25 12:17:53 -0600
committerJonathan Corbet <corbet@lwn.net>2011-03-25 14:30:31 -0600
commit5c050fb96380a87a85aad9084b68fdcd2b84c193 (patch)
treeb1d0bf29716a4e8a0da6d4b9b96bfe9635b58271 /Documentation/development-process/7.AdvancedTopics
parent9cad7962704d617ab1e4ae304baaaa22d727932b (diff)
downloadlinux-3.10-5c050fb96380a87a85aad9084b68fdcd2b84c193.tar.gz
linux-3.10-5c050fb96380a87a85aad9084b68fdcd2b84c193.tar.bz2
linux-3.10-5c050fb96380a87a85aad9084b68fdcd2b84c193.zip
docs: update the development process document
Here's a set of changes updating Documentation/development-process. I have update kernel releases and relevant statistics, added information for a couple of tools, zapped some trailing white space, and generally tried to make it more closely match the current state of affairs. [Typo fixes from Joe Perches and Nicolas Kaiser incorporated] Signed-off-by: Jonathan Corbet <corbet@lwn.net> Acked-by: Greg KH <greg@kroah.com> Cc: Randy Dunlap <rdunlap@xenotime.net>
Diffstat (limited to 'Documentation/development-process/7.AdvancedTopics')
-rw-r--r--Documentation/development-process/7.AdvancedTopics4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/development-process/7.AdvancedTopics b/Documentation/development-process/7.AdvancedTopics
index 837179447e1..26dc3fa196e 100644
--- a/Documentation/development-process/7.AdvancedTopics
+++ b/Documentation/development-process/7.AdvancedTopics
@@ -119,7 +119,7 @@ can affect your ability to get trees pulled in the future. Quoting Linus:
to trust things *without* then having to go and check every
individual change by hand.
-(http://lwn.net/Articles/224135/).
+(http://lwn.net/Articles/224135/).
To avoid this kind of situation, ensure that all patches within a given
branch stick closely to the associated topic; a "driver fixes" branch
@@ -138,7 +138,7 @@ When requesting a pull, be sure to give all the relevant information: where
your tree is, what branch to pull, and what changes will result from the
pull. The git request-pull command can be helpful in this regard; it will
format the request as other developers expect, and will also check to be
-sure that you have remembered to push those changes to the public server.
+sure that you have remembered to push those changes to the public server.
7.2: REVIEWING PATCHES