aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes/git-workflow
diff options
context:
space:
mode:
authorPaul Eggert2015-09-10 02:43:59 -0700
committerPaul Eggert2015-09-10 02:44:42 -0700
commitf962c5d6472804f788cdd54631bcc46aab5f59ce (patch)
treead7d748ad726126d4176594b80f3aa11f17dc935 /admin/notes/git-workflow
parent6ee7eabb5dbdf39f2d7471c9e42fc90c315e6a9f (diff)
downloademacs-f962c5d6472804f788cdd54631bcc46aab5f59ce.tar.gz
emacs-f962c5d6472804f788cdd54631bcc46aab5f59ce.zip
Add patch-sending instructions to git-workflow
From a suggestion by Mitchel Humpherys in: http://lists.gnu.org/archive/html/emacs-devel/2015-09/msg00421.html * admin/notes/git-workflow (Sending patches): New section.
Diffstat (limited to 'admin/notes/git-workflow')
-rw-r--r--admin/notes/git-workflow18
1 files changed, 18 insertions, 0 deletions
diff --git a/admin/notes/git-workflow b/admin/notes/git-workflow
index d1d105a8a7a..40dfa6b7410 100644
--- a/admin/notes/git-workflow
+++ b/admin/notes/git-workflow
@@ -46,6 +46,24 @@ top of that. Then say
46git push 46git push
47 47
48 48
49Sending patches
50===============
51
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
54change locally, do:
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
66
49Backporting to emacs-24 67Backporting to emacs-24
50======================= 68=======================
51 69