summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorVille Skyttä <ville.skytta@iki.fi>2011-06-18 15:59:32 +0300
committerVille Skyttä <ville.skytta@iki.fi>2011-06-18 15:59:32 +0300
commitae3be4b725d60ff711b3e82c6e4e6ade1a083865 (patch)
treedcb6c7f16c2f7cdb9f2b6aacf3d0aa932d77d24e /README
parent9e4605b68b19a36be15e077596ced66d04d91488 (diff)
downloadbash-completion-ae3be4b725d60ff711b3e82c6e4e6ade1a083865.tar.gz
README: Recommend git send-email.
Diffstat (limited to 'README')
-rw-r--r--README9
1 files changed, 5 insertions, 4 deletions
diff --git a/README b/README
index 52c4e1ea..67b79be2 100644
--- a/README
+++ b/README
@@ -366,10 +366,11 @@ guidelines in mind:
- Generate patches preferably against the git repository, with "git
format-patch origin/master" (assuming the diff was against the
- origin/master branch), and don't forget the entry for the CHANGES file
- if you feel that the change deserves one. If you don't have git
- available or can't access the repository for some reason, generate
- patches as unified diffs ('diff -u').
+ origin/master branch), and don't forget the entry for the CHANGES
+ file if you feel that the change deserves one, and send them
+ preferably with "git send-email". If you don't have git available
+ 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
portable to other platforms, so that everyone may enjoy it. If your