Make it clear that patches for *all* Xorg repos, including xserver,
should include the repo name in the [PATCH ...] prefix.

Signed-off-by: Alan Coopersmith <[email protected]>
---
 Development/Documentation/SubmittingPatches.mdwn |   13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/Development/Documentation/SubmittingPatches.mdwn 
b/Development/Documentation/SubmittingPatches.mdwn
index 2459ee9..94cd421 100644
--- a/Development/Documentation/SubmittingPatches.mdwn
+++ b/Development/Documentation/SubmittingPatches.mdwn
@@ -100,18 +100,19 @@ The subject line of the example patch:
 """]]
 The git format-patch command has prefixed the commit _subject line_ with the 
word [PATCH] on your behalf. If you haven't signed-off in the commit message 
body, you can do so with the --signoff option.  
 
-If you are submitting a patch for applications, drivers or libraries to 
xorg-devel list, you should add the component name next to the PATCH word using 
the --subject-prefix option. 
+The reviewers need to know for which component this patch is for when reading 
the e-mail or filtering in patchwork, as there are over 200 of them. You can 
configure the git format-patch and git send-email commands to always do it for 
you:
 
-Examples: 
 [[!format txt """
-[PATCH evdev] fix crash on VT switch #12345
-[PATCH libXi] convert to ANSI
+$> git config format.subjectprefix "PATCH evdev"
 """]]
-The reviewers need to know for which component this patch is for when reading 
the e-mail (there are over 200 of them). You can configure the git format-patch 
command to always do it for you: 
 
+Or you can add the component name next to the PATCH word using the 
--subject-prefix option to git format-patch and git send-email.
 
+Examples:
 [[!format txt """
-$> git config format.subjectprefix "PATCH evdev"
+[PATCH evdev] fix crash on VT switch #12345
+[PATCH libXi] convert to ANSI
+[PATCH xserver] randr: add support for holographic projector outputs
 """]]
 
 ## Extra info
-- 
1.7.9.2

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to