[PATCH 0/2] Describe patch-flow better in SubmittingPatches

[Junio C Hamano <gitster@pobox.com>]

So here is what I came up with.  The main idea behind this
"counter-proposal" is to make sure we do not add to the pile of
documents a new contributor needs to read before being able to send
"a perfect patch".  Reading SubmittingPatches alone should be
sufficient for them to understand what to expect and what are
expected of them.

Junio C Hamano (2):
  SubmittingPatches: move the patch-flow section earlier
  SubmittingPatches: extend the "flow" section

 Documentation/SubmittingPatches | 126 +++++++++++++++++++-------------
 1 file changed, 75 insertions(+), 51 deletions(-)

-- 
2.45.0-119-g0f3415f1f8