git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Symonds <dsymonds@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Consensus on "Git"
Date: Wed, 11 Nov 2009 04:27:31 -0500	[thread overview]
Message-ID: <20091111092731.GA17422@sigill.intra.peff.net> (raw)
In-Reply-To: <7v8wedv3a3.fsf@alter.siamese.dyndns.org>

On Wed, Nov 11, 2009 at 01:06:44AM -0800, Junio C Hamano wrote:

> > Is there consensus on "Git" being the standard capitalisation, versus
> > "GIT"?
> 
> I am not a consensus, but from day 1, Linus talked about "git" (all
> lowercase) and "Git" was used only when it came at the beginning of a
> sentence (an usual English capitalization rule) or in a section or book
> title where all words (except prepositions such as "in", "on") are
> capitalized, and I try to mimick it myself for consistency.
> 
> As a corollary, unless I spell all the other words in capital to SHOUT, I
> never write GIT.

Except for the title of every set of release notes, which all start
with:

  GIT vX.Y.Z Release Notes

? :)

For a fun (ab)use of blame, you can see who wrote each of David's
suspect lines with:

   git grep -n "\bGIT\b" |
   while IFS=: read file line junk; do
     git blame -f -L $line,$line $file
   done |
   less

Many of them are variables (e.g., \b gets rid of "_", but we still have
"-", so GIT-VERSION and such are still there). Many others are the title
of the "GIT" section of the manpages. But there are some legitimate
uses, too. Many of them blame to quite a long time ago, though (e.g.,
Documentation/everyday.txt has two uses by you in 2005).

-Peff

  reply	other threads:[~2009-11-11  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11  8:32 Consensus on "Git" David Symonds
2009-11-11  9:02 ` Sverre Rabbelier
2009-11-11  9:06 ` Junio C Hamano
2009-11-11  9:27   ` Jeff King [this message]
2009-11-11  9:36     ` Junio C Hamano
2009-11-11  9:36     ` Jeff King
2009-11-11  9:21 ` Reece Dunn
2009-11-11  9:33 ` Johannes Schindelin
2009-11-11 14:58   ` Teemu Likonen
2009-11-11 15:37     ` Michael J Gruber

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=20091111092731.GA17422@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=dsymonds@gmail.com \
    --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).