diff options
Diffstat (limited to 'admin/notes/git-workflow')
| -rw-r--r-- | admin/notes/git-workflow | 14 |
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 | ||
| 52 | If you lack push access or would like feedback before pushing a patch, | 52 | If you lack push access or would like feedback before pushing a patch, |
| 53 | you can send a patch file as a bug report. After committing your | 53 | you commit your change locally and then send a patch file as a bug report |
| 54 | change locally, do: | 54 | as described in ../../CONTRIBUTE. |
| 55 | |||
| 56 | git format-patch -1 | ||
| 57 | |||
| 58 | This creates a file 0001-DESCRIPTION.patch containing the patch, where | ||
| 59 | DESCRIPTION comes from the first line of your patch's commit message. | ||
| 60 | You can attach the patch file to email that you send to | ||
| 61 | bug-gnu-emacs@gnu.org. You can also configure git to email patches | ||
| 62 | directly (see <http://git-scm.com/docs/git-send-email>) and do: | ||
| 63 | |||
| 64 | git send-email --to=bug-gnu-emacs@gnu.org 0001-DESCRIPTION.patch | ||
| 65 | 55 | ||
| 66 | 56 | ||
| 67 | Backporting to emacs-24 | 57 | Backporting to emacs-24 |