README: Recommend git send-email.
This commit is contained in:
parent
9e4605b68b
commit
ae3be4b725
9
README
9
README
@ -366,10 +366,11 @@ guidelines in mind:
|
|||||||
|
|
||||||
- Generate patches preferably against the git repository, with "git
|
- Generate patches preferably against the git repository, with "git
|
||||||
format-patch origin/master" (assuming the diff was against the
|
format-patch origin/master" (assuming the diff was against the
|
||||||
origin/master branch), and don't forget the entry for the CHANGES file
|
origin/master branch), and don't forget the entry for the CHANGES
|
||||||
if you feel that the change deserves one. If you don't have git
|
file if you feel that the change deserves one, and send them
|
||||||
available or can't access the repository for some reason, generate
|
preferably with "git send-email". If you don't have git available
|
||||||
patches as unified diffs ('diff -u').
|
or can't access the repository for some reason, generate patches as
|
||||||
|
unified diffs ('diff -u').
|
||||||
|
|
||||||
- If your code was written for a particular platform, try to make it
|
- If your code was written for a particular platform, try to make it
|
||||||
portable to other platforms, so that everyone may enjoy it. If your
|
portable to other platforms, so that everyone may enjoy it. If your
|
||||||
|
Loading…
x
Reference in New Issue
Block a user