>From fa7f8cfe28a7b5bcca607f316d16322af17d206e Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 10 Sep 2015 11:21:17 -0700 Subject: [PATCH] * CONTRIBUTE: Move send-email here from git-workflow. --- CONTRIBUTE | 4 +++- admin/notes/git-workflow | 14 ++------------ 2 files changed, 5 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTE b/CONTRIBUTE index 7e697dd..5821ee5 100644 --- a/CONTRIBUTE +++ b/CONTRIBUTE @@ -234,7 +234,9 @@ by following links from http://savannah.gnu.org/mail/?group=emacs . To email a patch you can use a shell command like 'git format-patch -1' to create a file, and then attach the file to your email. This nicely -packages the patch's commit message and changes. +packages the patch's commit message and changes. To send just one +such patch without additional remarks, you can use a command like +'git send-email address@hidden 0001-DESCRIPTION.patch'. ** Document your changes. diff --git a/admin/notes/git-workflow b/admin/notes/git-workflow index 40dfa6b..92dc791 100644 --- a/admin/notes/git-workflow +++ b/admin/notes/git-workflow @@ -50,18 +50,8 @@ Sending patches =============== If you lack push access or would like feedback before pushing a patch, -you can send a patch file as a bug report. After committing your -change locally, do: - -git format-patch -1 - -This creates a file 0001-DESCRIPTION.patch containing the patch, where -DESCRIPTION comes from the first line of your patch's commit message. -You can attach the patch file to email that you send to address@hidden You can also configure git to email patches -directly (see ) and do: - -git send-email address@hidden 0001-DESCRIPTION.patch +you commit your change locally and then send a patch file as a bug report +as described in ../../CONTRIBUTE. Backporting to emacs-24 -- 2.1.0