Skip to contentSkip to conversation

SubmittingPatches: Fix reference to renumbered step

PATCH In review Michael Brunner 3 participants 3 messages Aug 3, 2009 – Aug 8, 2009 Documentation

lore
Share & tools
lore

Michael Brunner

author
#0 lore raw

PATCH 1/1 SubmittingPatches: Fix reference to renumbered step

This patch fixes a reference to step "Select e-mail destination." which has been renumbered from 4) to 5) in linux-2.6.22.

Signed-off-by Michael Brunner <[email protected]>

---

 Documentation/SubmittingPatches |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/SubmittingPatches +1 -1
index 5c555a8..b7f9d3b 100644
@@ -183,7 +183,7 @@ the MAN-PAGES maintainer (as listed in the MAINTAINERS file)
 a man-pages patch, or at least a notification of the change,
 so that some information makes its way into the manual pages.
 
-Even if the maintainer did not respond in step #4, make sure to ALWAYS
+Even if the maintainer did not respond in step #5, make sure to ALWAYS
 copy the maintainer when you change their code.
 
 For small patches you may want to CC the Trivial Patch Monkey
Acked-by on v1 1/1
#1 lore raw
Quoted 4 lines · On Tue, 4 Aug 2009 00:41:11 +0200 Michael Brunner wrote:

This patch fixes a reference to step "Select e-mail destination." which has been renumbered from 4) to 5) in linux-2.6.22.

Signed-off-by Michael Brunner <[email protected]>
Acked-by Randy Dunlap <[email protected]>

Jiri, will you merge this, please?

Quoted 10 lines

---

 Documentation/SubmittingPatches |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/SubmittingPatches +0 -0
index 5c555a8..b7f9d3b 100644

Documentation/SubmittingPatches the MAN-PAGES maintainer (as listed in the MAINTAINERS file) · line 189

Quoted 8 lines
Documentation/SubmittingPatches +1 -1
@@ -183,7 +183,7 @@ the MAN-PAGES maintainer (as listed in the MAINTAINERS file)
 a man-pages patch, or at least a notification of the change,
 so that some information makes its way into the manual pages.
 
-Even if the maintainer did not respond in step #4, make sure to ALWAYS
+Even if the maintainer did not respond in step #5, make sure to ALWAYS
 copy the maintainer when you change their code.
 
 For small patches you may want to CC the Trivial Patch Monkey

---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/