Documentation/SubmittingPatches: discuss first then submit
This is something I've had in mind for some time. I get enough e-mails as-is, and I suspect the workflow to get list members involved would work better if we get the discussion concluded on the list first before patches hit my tree (even 'next'). Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Feb 3, 2008 at 17:00 UTC
0b0599402d0e4354c60d192eb926f46577040a29
1 file changed
+5
-4
Documentation/SubmittingPatches
+5
-4
@@ -34,9 +34,9 @@ Checklist (and a short version for the impatient):
34
- if your name is not writable in ASCII, make sure that
35
you send off a message in the correct encoding.
36
- send the patch to the list (git@vger.kernel.org) and the
37
- maintainer (gitster@pobox.com). If you use
38
- git-send-email(1), please test it first by sending
39
- email to yourself.
37
+ maintainer (gitster@pobox.com) if (and only if) the patch
38
+ is ready for inclusion. If you use git-send-email(1),
39
+ please test it first by sending email to yourself.
40
41
Long version:
42
@@ -162,7 +162,8 @@ Note that your maintainer does not necessarily read everything
162
on the git mailing list. If your patch is for discussion first,
163
send it "To:" the mailing list, and optionally "cc:" him. If it
164
is trivially correct or after the list reached a consensus, send
165
-it "To:" the maintainer and optionally "cc:" the list.
165
+it "To:" the maintainer and optionally "cc:" the list for
166
+inclusion.
167
168
Also note that your maintainer does not actively involve himself in
169
maintaining what are in contrib/ hierarchy. When you send fixes and