aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes/git-workflow
diff options
context:
space:
mode:
authorPaul Eggert2015-09-11 08:34:46 -0700
committerPaul Eggert2015-09-11 08:34:46 -0700
commit279303adfc6d6ba91db788c2b85333e3fc46f39b (patch)
tree3fe9c0b6ca485d35b9549d25c6f250d1c1b40e5a /admin/notes/git-workflow
parenta0ec54ae073abd671bd43002eff0267f5fe8b306 (diff)
downloademacs-279303adfc6d6ba91db788c2b85333e3fc46f39b.tar.gz
emacs-279303adfc6d6ba91db788c2b85333e3fc46f39b.zip
* CONTRIBUTE: Move send-email here from git-workflow.
Diffstat (limited to 'admin/notes/git-workflow')
-rw-r--r--admin/notes/git-workflow14
1 files changed, 2 insertions, 12 deletions
diff --git a/admin/notes/git-workflow b/admin/notes/git-workflow
index 40dfa6b7410..92dc79127e3 100644
--- a/admin/notes/git-workflow
+++ b/admin/notes/git-workflow
@@ -50,18 +50,8 @@ Sending patches
50=============== 50===============
51 51
52If you lack push access or would like feedback before pushing a patch, 52If you lack push access or would like feedback before pushing a patch,
53you can send a patch file as a bug report. After committing your 53you commit your change locally and then send a patch file as a bug report
54change locally, do: 54as described in ../../CONTRIBUTE.
55
56git format-patch -1
57
58This creates a file 0001-DESCRIPTION.patch containing the patch, where
59DESCRIPTION comes from the first line of your patch's commit message.
60You can attach the patch file to email that you send to
61bug-gnu-emacs@gnu.org. You can also configure git to email patches
62directly (see <http://git-scm.com/docs/git-send-email>) and do:
63
64git send-email --to=bug-gnu-emacs@gnu.org 0001-DESCRIPTION.patch
65 55
66 56
67Backporting to emacs-24 57Backporting to emacs-24