From ac8000806d8d23c9171656197f8c889936962a3e Mon Sep 17 00:00:00 2001 From: Mike Swanson Date: Fri, 8 May 2009 17:41:49 -0700 Subject: [PATCH] Replace reasoning of `git commit -s` in the README Found out a couple months ago that it doesn't work the way I had assumed, although it still has a useful purpose. Signed-off-by: Mike Swanson --- README | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README b/README index 262a6bd1..b6fe034c 100644 --- a/README +++ b/README @@ -144,9 +144,12 @@ You should prefix this line with the component you are committing (for example, ``map17: fixed unbeatable map''). This should be followed by a blank line and a paragraph or more to explain your change in detail (for example, explaining what part of the map was broken). See commit -27762aa5f34f590bfc29d1f667f9121907cb8a98 for an example. If you use -GPG, try to sign your commits with `git commit -s` if possible; this -ensures that you are who you say you are. +27762aa5f34f590bfc29d1f667f9121907cb8a98 for an example. Sign your +comments with `git commit -s`, these leaves a trail of whose hands a +commit went through and could be useful for some purposes; git alone can +give an indication of up to two people, however the AUTHOR/COMMITER +fields are not quite reliable or flexible enough for the same +information. You should commit often; each important change should get its own commit, but minor changes need not. Take advantage of git's ability to