It was indeed not obvious for new contributors to find this document in the source tree, since there were no reference to it outside the Documentation/ directory. Signed-off-by: Matthieu Moy <Matthieu.Moy@xxxxxxx> --- > Thank you for the advice, I read README file (couldn't find a HACKING > one) and the git website, and neither of those had a reference to > SubmittingPatches.. Indeed. As a bonnus, here's a submission that should match the guidelines (above --- is the commit message, and here is the place for free comments). README | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/README b/README index 67cfeb2..d2690ec 100644 --- a/README +++ b/README @@ -42,10 +42,12 @@ including full documentation and Git related tools. The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature -requests, comments and patches to git@xxxxxxxxxxxxxxx. To subscribe -to the list, send an email with just "subscribe git" in the body to -majordomo@xxxxxxxxxxxxxxx. The mailing list archives are available at -http://marc.theaimsgroup.com/?l=git and other archival sites. +requests, comments and patches to git@xxxxxxxxxxxxxxx (read +Documentation/SubmittingPatches for instructions on patch submission). +To subscribe to the list, send an email with just "subscribe git" in +the body to majordomo@xxxxxxxxxxxxxxx. The mailing list archives are +available at http://marc.theaimsgroup.com/?l=git and other archival +sites. The messages titled "A note from the maintainer", "What's in git.git (stable)" and "What's cooking in git.git (topics)" and -- 1.7.9.111.gf3fb0.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html