aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-09-20 11:29:43 +0200
committerMattias Andrée <maandree@operamail.com>2013-09-20 11:29:43 +0200
commitcc95b29656018bf8cb42e6f8077b9586beb4a850 (patch)
tree936371fa54b7be109c5e0ae34beb653d46b0ed2c
parentadd style to shorthand list (diff)
downloadusing-git-cc95b29656018bf8cb42e6f8077b9586beb4a850.tar.gz
using-git-cc95b29656018bf8cb42e6f8077b9586beb4a850.tar.bz2
using-git-cc95b29656018bf8cb42e6f8077b9586beb4a850.tar.xz
shorthands are not too bad because they are accompanied by code, but never do it for patches and pull requests
Signed-off-by: Mattias Andrée <maandree@operamail.com>
-rw-r--r--using-git.texinfo5
1 files changed, 4 insertions, 1 deletions
diff --git a/using-git.texinfo b/using-git.texinfo
index 74aba44..412904c 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -1796,7 +1796,10 @@ very friendly in this respect as create
a commit is lightning fast, and photon
fast in comparsing to other old school
source control systems.}. Because of this
-you may need to compromise your messages,
+you may need to compromise your messages
+--- which is not too bad because they are
+accompanied by code, but never do it when
+submitting patches or pull requests ---
one thing you can do is to not describe
a fix bug if it should be obvious for
the changeset@footnote{Can only be obvious