Commit 279303ad authored by Paul Eggert's avatar Paul Eggert
Browse files

* CONTRIBUTE: Move send-email here from git-workflow.

parent a0ec54ae
......@@ -234,7 +234,9 @@ by following links from .
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 0001-DESCRIPTION.patch'.
** Document your changes.
......@@ -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 You can also configure git to email patches
directly (see <>) and do:
git send-email 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
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment