From: Linus Torvalds <torvalds@osdl.org>
To: Aaron Gray <angray@beeb.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Why's Git called Git ?
Date: Mon, 3 Jul 2006 20:28:16 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607032022050.12404@g5.osdl.org> (raw)
In-Reply-To: <013001c69f04$ae4e2400$0200a8c0@amd2500>
On Tue, 4 Jul 2006, Aaron Gray wrote:
>
> Why the name I could not find any answer in the documentation ?
It's really quite random. It needs to be a two- or three-letter thing just
because I end up typing a lot.
My favourite explanation is "I name all my projects after myself: first
'Linux', now 'git'".
Which only makes sense if you know british slang.
The runner up was "Because 'twerp' was too hard to type".
But really, there's not a lot of real thinking behind it. The made-up
acronym was "global information tracker", but that's a pretty bad excuse
too.
It just happened. Don't ask me why. All the explanations are really made
up after the fact.
Linus
next prev parent reply other threads:[~2006-07-04 3:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 0:56 Why's Git called Git ? Aaron Gray
2006-07-04 3:28 ` Linus Torvalds [this message]
2006-07-05 19:58 ` Aaron Gray
2006-07-05 19:33 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 2:18 Aaron Gray
2006-07-07 18:40 ` Jakub Narebski
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=Pine.LNX.4.64.0607032022050.12404@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=angray@beeb.net \
--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).