git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: David Symonds <dsymonds@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Consensus on "Git"
Date: Wed, 11 Nov 2009 16:58:47 +0200	[thread overview]
Message-ID: <87y6mdyuoo.fsf@iki.fi> (raw)
In-Reply-To: <alpine.DEB.1.00.0911111028040.19111@intel-tinevez-2-302> (Johannes Schindelin's message of "Wed, 11 Nov 2009 10:33:20 +0100 (CET)")

On 2009-11-11 10:33 (+0100), Johannes Schindelin wrote:

> Yes, in Open Source, we are used to crude, geeky humor, some of us
> even accept blunt mails, but we are embedded in a world that is called
> "reality".
>
> In my experience, in this world it is much easier to tell people that
> your program is called "Git" ("could have been John, either") and be
> done with the questions.

Yes, that’s how the language works. Proper nouns are capitalized, so in
plain text the name of this program should always be written “Git”. Only
in command examples it is “git”.

Sometimes people mix proper nouns and logos/brands. Proper nouns are
under the rules of the language. For example, I can’t go telling people
that my name must be written “teEMu” because I don’t own Finnish.

In logos the brands’ owner can try to be funny and cool and different
and write anything they want (like “gɨT” or “GīT”).

  reply	other threads:[~2009-11-11 14:59 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
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 [this message]
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=87y6mdyuoo.fsf@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    /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).