You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: notes.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,19 @@
1
+
In http://git-scm.com/docs/git-format-patch :
2
+
3
+
--subject-prefix=<Subject-Prefix>
4
+
Instead of the standard [PATCH] prefix in the subject line, instead use [<Subject-Prefix>]. This allows for useful naming of a patch series, and can be combined with the --numbered option.
5
+
6
+
[PATCH v2 ...]
7
+
[RFC/PATCH ...]
8
+
[WIP/PATCH v4 6/8]
9
+
[PATCH]
10
+
[RFC/WIP PATCH 06/11]
11
+
[PATCH/WIP 4/8]
12
+
13
+
Matthieu Moy said: I found no way to specify a version like [PATCH v2 ...]. Similarly, there could be a way to say [RFC/PATCH ...].
14
+
15
+
16
+
1
17
Potential features TODO:
2
18
3
19
* When closing a PR 'cos it's been posted, link to http://mid.gmane.org/1234567890.1234567890@example.com so we can see the discussion.
0 commit comments