* Why's Git called Git ?
@ 2006-07-04 0:56 Aaron Gray
2006-07-04 3:28 ` Linus Torvalds
0 siblings, 1 reply; 6+ messages in thread
From: Aaron Gray @ 2006-07-04 0:56 UTC (permalink / raw)
To: Git Mailing List
Why the name I could not find any answer in the documentation ?
Aaron
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why's Git called Git ?
2006-07-04 0:56 Why's Git called Git ? Aaron Gray
@ 2006-07-04 3:28 ` Linus Torvalds
2006-07-05 19:58 ` Aaron Gray
0 siblings, 1 reply; 6+ messages in thread
From: Linus Torvalds @ 2006-07-04 3:28 UTC (permalink / raw)
To: Aaron Gray; +Cc: Git Mailing List
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why's Git called Git ?
2006-07-05 19:58 ` Aaron Gray
@ 2006-07-05 19:33 ` Jakub Narebski
0 siblings, 0 replies; 6+ messages in thread
From: Jakub Narebski @ 2006-07-05 19:33 UTC (permalink / raw)
To: git
Aaron Gray wrote:
> Anyway good going, I am glad Linux has an open source VCS again now.
>
> I do not know how BitKeeper are going to fell knowing they have been
> replaced by a Git :)
>
> I am toying with using a VCS for a set of related projects, either CVS
> because its well known, SubVersion for ease of use, or Git as it is new.
> Lots to descide upon, any pointers would be appreciated.
CVS is showing it's age; mainly the fact that IIRC it began as a series of
scripts over RCS, file level version control system, extending version
control to sets of files, somewhat. Branching in CVS is serious PITA.
Renaming _with_ retaining full and correct history: forget about it.
Subversion is "better CVS": still centralized, CVS infernal branching
replaced by "cheap copy" branching. Well known, replaces CVS thorough OSS
projects.
Git, Mercurial, Monotone, Bazaar-NG, Darcs are new brand of distributed VCS.
I really like notion of branching in Git; but be warned about tracking and
not recording renames, and the need of explicit packing (the latter very
minor). Powerfull, perhaps too powerfull for newbie user: but that is what
Cogito is for (although now Git contains fairly large set of high-level
commands).
http://git.or.cz/
http://git.or.cz/gitwiki
http://git.or.cz/gitwiki/Git
and "Other version control software" at
http://git.or.cz/gitwiki/GitLinks
P.S. If you decide to use Git as VCS for your project, consider adding entry
about it on http://git.or.cz/gitwiki/GitProjects wiki page.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git (at FreeNode)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why's Git called Git ?
2006-07-04 3:28 ` Linus Torvalds
@ 2006-07-05 19:58 ` Aaron Gray
2006-07-05 19:33 ` Jakub Narebski
0 siblings, 1 reply; 6+ messages in thread
From: Aaron Gray @ 2006-07-05 19:58 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Git Mailing List
Anyway good going, I am glad Linux has an open source VCS again now.
I do not know how BitKeeper are going to fell knowing they have been
replaced by a Git :)
I am toying with using a VCS for a set of related projects, either CVS
because its well known, SubVersion for ease of use, or Git as it is new.
Lots to descide upon, any pointers would be appreciated.
All the best to the Git team.
Regards,
Aaron
----- Original Message -----
From: "Linus Torvalds" <torvalds@osdl.org>
To: "Aaron Gray" <angray@beeb.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Sent: Tuesday, July 04, 2006 4:28 AM
Subject: Re: Why's Git called Git ?
>
>
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Why's Git called Git ?
@ 2006-07-06 2:18 Aaron Gray
2006-07-07 18:40 ` Jakub Narebski
0 siblings, 1 reply; 6+ messages in thread
From: Aaron Gray @ 2006-07-06 2:18 UTC (permalink / raw)
To: Git Mailing List
>> I am toying with using a VCS for a set of related projects, either CVS
>> because its well known, SubVersion for ease of use, or Git as it is new.
>> Lots to descide upon, any pointers would be appreciated.
>
> CVS is showing it's age; mainly the fact that IIRC it began as a series of
> scripts over RCS, file level version control system, extending version
> control to sets of files, somewhat. Branching in CVS is serious PITA.
> Renaming _with_ retaining full and correct history: forget about it.
Okay, we like branching and forking.
> Subversion is "better CVS": still centralized, CVS infernal branching
> replaced by "cheap copy" branching. Well known, replaces CVS thorough OSS
> projects.
Okay.
> Git, Mercurial, Monotone, Bazaar-NG, Darcs are new brand of distributed
> VCS.
> I really like notion of branching in Git; but be warned about tracking and
> not recording renames, and the need of explicit packing (the latter very
> minor). Powerfull, perhaps too powerfull for newbie user: but that is what
> Cogito is for (although now Git contains fairly large set of high-level
> commands).
We like to move forward.
>
> http://git.or.cz/
> http://git.or.cz/gitwiki
> http://git.or.cz/gitwiki/Git
> and "Other version control software" at
> http://git.or.cz/gitwiki/GitLinks
Yes, been there, thanks though.
> P.S. If you decide to use Git as VCS for your project, consider adding
> entry
> about it on http://git.or.cz/gitwiki/GitProjects wiki page.
Looks like I maybe doing a preliminary Windows Git HOWTO on the GitWiki, if
no one else has trod this ground :) (Might need some proper help testing
though)
Thanks,
Aaron
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why's Git called Git ?
2006-07-06 2:18 Aaron Gray
@ 2006-07-07 18:40 ` Jakub Narebski
0 siblings, 0 replies; 6+ messages in thread
From: Jakub Narebski @ 2006-07-07 18:40 UTC (permalink / raw)
To: git
Aaron Gray wrote:
>> I really like notion of branching in Git; but be warned about tracking and
>> not recording renames, and the need of explicit packing (the latter very
>> minor). Powerfull, perhaps too powerfull for newbie user: but that is what
>> Cogito is for (although now Git contains fairly large set of high-level
>> commands).
>
> We like to move forward.
What I like a lot in Git is very easy switching of working area between
branches, and to arbitrary commit (point in history).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-07-07 18:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-04 0:56 Why's Git called Git ? Aaron Gray
2006-07-04 3:28 ` Linus Torvalds
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
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).