diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2015-09-10 02:43:59 -0700 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2015-09-10 02:44:42 -0700 |
| commit | f962c5d6472804f788cdd54631bcc46aab5f59ce (patch) | |
| tree | ad7d748ad726126d4176594b80f3aa11f17dc935 /admin | |
| parent | 6ee7eabb5dbdf39f2d7471c9e42fc90c315e6a9f (diff) | |
| download | emacs-f962c5d6472804f788cdd54631bcc46aab5f59ce.tar.gz emacs-f962c5d6472804f788cdd54631bcc46aab5f59ce.tar.bz2 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')
| -rw-r--r-- | admin/notes/git-workflow | 18 |
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 git push +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 +bug-gnu-emacs@gnu.org. You can also configure git to email patches +directly (see <http://git-scm.com/docs/git-send-email>) and do: + +git send-email --to=bug-gnu-emacs@gnu.org 0001-DESCRIPTION.patch + + Backporting to emacs-24 ======================= |