From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Unify use of [sha,SHA][,-]1
Date: Fri, 24 Apr 2009 16:49:33 +0200 [thread overview]
Message-ID: <1240584575-5702-1-git-send-email-git@drmicha.warpmail.net> (raw)
a6e5ef7 (user-manual: the name of the hash function is SHA-1, not sha1,
2009-04-04) made sure the user manual names the hash "SHA-1" only. This
series achieves the same for the rest of the documentation.
I split it into two parts for replacing "sha1" and "SHA1". The form
"sha-1" did not appear anywhere.
I went through each replacement manually: code samples etc. should not be
transformed. Each commit messsage lists the exceptions.
The diffstat may look a bit frightening but the patch can be reviewed
most easily with --color-words. I'd be happy to be split it up further
but didn't see any obvious splitting boundaries. (I would point to
http://repo.or.cz/w/git/mjg.git?h=refs/heads/doc-use-SHA-1 if gitweb
had commitdiff-colorwords.)
Cheers,
Michael
Suggested by: Ulrich Windl
Michael J Gruber (2):
Documentation: replace sha1 by SHA-1
Documentation: replace SHA1 by SHA-1
Documentation/config.txt | 2 +-
Documentation/diff-format.txt | 8 ++--
Documentation/git-blame.txt | 4 +-
Documentation/git-branch.txt | 8 ++--
Documentation/git-cat-file.txt | 10 +++---
Documentation/git-cherry.txt | 4 +-
Documentation/git-cvsexportcommit.txt | 4 +-
Documentation/git-describe.txt | 2 +-
Documentation/git-diff-index.txt | 8 ++--
Documentation/git-filter-branch.txt | 6 ++--
Documentation/git-fsck.txt | 12 ++++----
Documentation/git-index-pack.txt | 2 +-
Documentation/git-init.txt | 2 +-
Documentation/git-ls-files.txt | 2 +-
Documentation/git-merge-index.txt | 2 +-
Documentation/git-mktag.txt | 2 +-
Documentation/git-name-rev.txt | 2 +-
Documentation/git-pack-objects.txt | 2 +-
Documentation/git-patch-id.txt | 2 +-
Documentation/git-receive-pack.txt | 32 ++++++++++----------
Documentation/git-reflog.txt | 4 +-
Documentation/git-rev-parse.txt | 8 ++--
Documentation/git-show-branch.txt | 4 +-
Documentation/git-show-index.txt | 2 +-
Documentation/git-show-ref.txt | 4 +-
Documentation/git-svn.txt | 4 +-
Documentation/git-tag.txt | 2 +-
Documentation/git-unpack-file.txt | 2 +-
Documentation/git-update-index.txt | 14 ++++----
Documentation/git-update-ref.txt | 8 ++--
Documentation/git-verify-pack.txt | 4 +-
Documentation/git-verify-tag.txt | 2 +-
Documentation/git.txt | 12 ++++----
Documentation/gitcore-tutorial.txt | 8 ++--
Documentation/gitdiffcore.txt | 2 +-
Documentation/githooks.txt | 2 +-
Documentation/gittutorial-2.txt | 16 +++++-----
Documentation/glossary-content.txt | 8 ++--
.../howto/recover-corrupted-blob-object.txt | 6 ++--
Documentation/howto/update-hook-example.txt | 6 ++--
Documentation/pretty-formats.txt | 16 +++++-----
Documentation/technical/pack-format.txt | 14 ++++----
Documentation/technical/pack-protocol.txt | 20 ++++++------
Documentation/technical/shallow.txt | 4 +-
44 files changed, 144 insertions(+), 144 deletions(-)
next reply other threads:[~2009-04-24 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 14:49 Michael J Gruber [this message]
2009-04-24 14:49 ` [PATCH 1/2] Documentation: replace sha1 by SHA-1 Michael J Gruber
2009-04-24 14:49 ` [PATCH 2/2] Documentation: replace SHA1 " Michael J Gruber
2009-04-24 21:30 ` Jeff King
2009-04-24 15:18 ` [PATCH 1/2] Documentation: replace sha1 " Johannes Sixt
2009-04-24 15:23 ` Wincent Colaiuta
2009-04-24 15:33 ` Michael J Gruber
2009-04-24 15:30 ` Michael J Gruber
2009-04-24 21:28 ` Jeff King
2009-04-24 22:38 ` Junio C Hamano
2009-04-25 10:47 ` Felipe Contreras
2009-04-25 12:13 ` Dmitry Potapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1240584575-5702-1-git-send-email-git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).