projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4e891ac) | patch
Documentation/SubmittingPatches: discuss first then submit
authorJunio C Hamano <gitster@pobox.com>
Mon, 4 Feb 2008 01:00:16 +0000 (17:00 -0800)
committerJunio C Hamano <gitster@pobox.com>
Tue, 5 Feb 2008 08:39:03 +0000 (00:39 -0800)
commit0b0599402d0e4354c60d192eb926f46577040a29
tree05396080bae47a8af3d591633486db350d6d394dtree | snapshot
parent4e891acf679c0020b61889447f8f412324aeffa9commit | diff
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>
Documentation/SubmittingPatches diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.