[PATCH] * git-workflow: Add instructions for sending patch files

[Mitchel Humpherys]

While there are some vague references to `git format-patch' in a few
places, it can be unclear to new developers what the preferred method is
for sending in "drive-by" patches.  Fix this by adding explicit
instructions to the git-workflow file.
---
 admin/notes/git-workflow | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/admin/notes/git-workflow b/admin/notes/git-workflow
index d1d105a8a7..edea7a652e 100644
--- a/admin/notes/git-workflow
+++ b/admin/notes/git-workflow
@@ -46,6 +46,21 @@ top of that.  Then say
 git push
 
 
+Sending Patches
+===============
+
+If you don't have push access to the main repository, or if you'd
+simply like some feedback on a patch before pushing it, you can send a
+patch file to the mailing list.  After committing your change locally,
+do:
+
+git format-patch -1
+git send-email --to address@hidden YOUR-PATCH-FILE.patch
+
+You'll need to configure git to be able to send email as described in
+http://git-scm.com/docs/git-send-email
+
+
 Backporting to emacs-24
 =======================
 
-- 
2.5.1