diff options
| author | Adam Dinwoodie <adam@dinwoodie.org> | 2017-11-10 15:02:50 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2017-11-11 03:07:03 +0900 |
| commit | f6be7edcacd3acb2c4eb3386eb51c991bfdc8a6f (patch) | |
| tree | 30462930f4db5d5f931d310be346a977182a63d9 /git-gui/lib/merge.tcl | |
| parent | cb5918aa0d50f50e83787f65c2ddc3dcb10159fe (diff) | |
| download | git-f6be7edcacd3acb2c4eb3386eb51c991bfdc8a6f.tar.gz git-f6be7edcacd3acb2c4eb3386eb51c991bfdc8a6f.tar.xz | |
doc/SubmittingPatches: correct subject guidance
The examples and common practice for adding markers such as "RFC" or
"v2" to the subject of patch emails is to have them within the same
brackets as the "PATCH" text, not after the closing bracket. Further,
the practice of `git format-patch` and the like, as well as what appears
to be the more common pratice on the mailing list, is to use "[RFC
PATCH]", not "[PATCH/RFC]".
Update the SubmittingPatches article to match and to reference the
`format-patch` helper arguments, and also make some minor text
clarifications in the area.
Signed-off-by: Adam Dinwoodie <adam@dinwoodie.org>
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-gui/lib/merge.tcl')
0 files changed, 0 insertions, 0 deletions