v2 incorporates the changes as discussed so far. It comes with three bonus patches which enforce the use of lowercase <identifiers> (as per CodingGuidelines) in command messages (usage). Besides the guidelines, this is also the prevailing style in code. Documentation is a different issue. patches 1,3,5 are unchanged wrt v1. The last 3 are divided according to the grep expressions which I used to identify candidates. Michael J Gruber (10): commit,tag: use same wording for -F commit,status: describe --porcelain just like push clone,init: describe --template using the same wording commit,merge,tag: describe -m likewise add: describe --patch like checkout, reset commit,status: describe -u likewise git-tag.txt: list all modes in the description Make <identifier> lowercase as per CodingGuidelines Make <identifier> lowercase as per CodingGuidelines Make <identifier> lowercase as per CodingGuidelines Documentation/git-tag.txt | 11 ++++++----- builtin/add.c | 2 +- builtin/clone.c | 4 ++-- builtin/commit.c | 22 +++++++++++----------- builtin/config.c | 2 +- builtin/fast-export.c | 4 ++-- builtin/fetch.c | 6 +++--- builtin/init-db.c | 2 +- builtin/merge.c | 2 +- builtin/notes.c | 16 ++++++++-------- builtin/read-tree.c | 4 ++-- builtin/tag.c | 6 +++--- parse-options.h | 2 +- t/t0040-parse-options.sh | 2 +- test-parse-options.c | 2 +- 15 files changed, 44 insertions(+), 43 deletions(-) -- 1.7.4.1.74.gf39475.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html