Development using git:Creating patches: Difference between revisions
Itoffshore (talk | contribs) m (fix git send-mail for multiple patches) |
(improve example commit message) |
||
Line 10: | Line 10: | ||
<pre> | <pre> | ||
testing/packagename: new aport <- Subject line | |||
Enter some details about your package <- Mail body | Enter some details about your package <- Mail body | ||
here if you like. | here if you like and an url where to find more information | ||
http://example.com/packagename | |||
</pre> | </pre> | ||
Revision as of 10:29, 7 June 2015
Patches should be created with git and submitted to alpine-aports mailing list with git send-email.
Only the last commit with 'git send-email'
To submit the last commit as a patch to alpine-aports mailing list:
git send-email --to alpine-aports@lists.alpinelinux.org HEAD^
The first line in commit message will be subject and the long description (separated with empty line) will be the body in the email. The example below shows
testing/packagename: new aport <- Subject line Enter some details about your package <- Mail body here if you like and an url where to find more information http://example.com/packagename
Read Development using git to send patch with SMTP Auth.
Multiple commits with 'git send-email'
If you have many commits you can create a directory with patches and send them with git send-email.
rm -Rf patches mkdir patches git format-patch -o patches origin git send-email patches --compose --no-chain-reply-to --to alpine-aports@lists.alpinelinux.org
You can also format patches for the last x number of commits with:
git format-patch -x -o patches
This will produce the patches for each local commit in the directory "patches" and send them. Use --no-chain-reply-to make sure it doesn't reply.
Don't do:
- [PATCH 0/m]
- [PATCH 1/m]
- [PATCH 2/m]
- ...
- [PATCH 2/m]
- [PATCH 1/m]
But do:
- [PATCH 0/m]
- [PATCH 1/m]
- [PATCH 2/m]
- ..