diff options
| author | Mattias Andrée <maandree@operamail.com> | 2013-08-16 03:17:10 +0200 |
|---|---|---|
| committer | Mattias Andrée <maandree@operamail.com> | 2013-08-16 03:17:10 +0200 |
| commit | 77fcd287cfde266cba5df35cb6bb766d76dc9dda (patch) | |
| tree | 6e72c91b48278be6b2e9566687fa08041c624816 /using-git.texinfo | |
| parent | creating a patch (diff) | |
| download | using-git-77fcd287cfde266cba5df35cb6bb766d76dc9dda.tar.gz using-git-77fcd287cfde266cba5df35cb6bb766d76dc9dda.tar.bz2 using-git-77fcd287cfde266cba5df35cb6bb766d76dc9dda.tar.xz | |
subject line prefix
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to 'using-git.texinfo')
| -rw-r--r-- | using-git.texinfo | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/using-git.texinfo b/using-git.texinfo index fe40278..c62bf0f 100644 --- a/using-git.texinfo +++ b/using-git.texinfo @@ -519,6 +519,16 @@ it can easily be submitted to a mailing list, which the common way for large projects for accepting patches. +The created patch file is formated as an +e-mail, with `[PATCH]' in the beginning of +the subject line. If you update the patch +it is customary to use `[PATCH v2]' instread +and `[PATCH v3]' on the second update. +If the patch, however it not readly for +being included, but is rather for discussion, +use `PATCH/RFC'@footnote{RFC is an abbreviation +for `Request for comments'} instead of `PATCH'. + |