From c88f4b9a775d268431d0f132d7de79ccb455c33a Mon Sep 17 00:00:00 2001 From: Mike Swanson Date: Fri, 17 Sep 2010 02:19:13 -0700 Subject: [PATCH] Change example commit in README and fix formatting in asciidoc. The commit referenced was from prior to the history-rewrite and no longer was a real commit in the repository. Also, asciidoc had some formatting error in the "Submitting your work" section where a large chungy of text was being rendered as monospace in the HTML version. To fix this, "git commit -s" is surrounded by +s rather than `s. Signed-off-by: Mike Swanson --- README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index da3ac70d..793c32f9 100644 --- a/README +++ b/README @@ -144,8 +144,8 @@ 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. Sign your -comments with `git commit -s`, these leaves a trail of whose hands a +49dc6ca861d4b85ca16b219941ecb86d3e172ac1 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