From: David Greaves <david@dgreaves•com>
To: Steven Cole <elenstev@mesatop•com>
Cc: Petr Baudis <pasky@ucw•cz>, git@vger•kernel.org
Subject: Re: [PATCH] Add help details to git help command. (This time with Perl)
Date: Tue, 19 Apr 2005 21:45:17 +0100 [thread overview]
Message-ID: <42656DDD.2090907@dgreaves.com> (raw)
In-Reply-To: <42656B6B.3080209@mesatop.com>
Steven Cole wrote:
> Speaking of "I think", the name "cogito" was suggested for the
> SCM layer, but IIRC Linus suggested staying with just plain git. Petr
> suggested tig, perhaps because it looks at git from another point of view.
I haven't read _all_ the mails - I thought cogito was kinda selected and
I got the feeling that Linus wasn't exactly bothered what it was called.
Anyway, git has a rename that needs testing at some point...
> legit Since git is GPLv2, but perhaps a little too French.
That made me smile.
Quite a few entendres in there...
It's Petr's baby - he gets to name it.
David
next prev parent reply other threads:[~2005-04-19 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 4:42 [PATCH] Add help details to git help command Steven Cole
2005-04-18 10:24 ` Petr Baudis
2005-04-18 16:59 ` Steven Cole
2005-04-19 1:40 ` [RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.) Steven Cole
2005-04-19 1:51 ` Petr Baudis
2005-04-19 14:41 ` David Greaves
2005-04-19 16:03 ` Steven Cole
2005-04-19 17:32 ` Petr Baudis
2005-04-19 17:35 ` [PATCH] Add help details to git help command. (This time with Perl) Steven Cole
2005-04-19 17:50 ` Petr Baudis
2005-04-19 19:04 ` David Greaves
2005-04-19 20:34 ` Steven Cole
2005-04-19 20:45 ` David Greaves [this message]
2005-04-20 23:34 ` Petr Baudis
2005-04-21 9:29 ` David Greaves
2005-04-23 23:41 ` Petr Baudis
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=42656DDD.2090907@dgreaves.com \
--to=david@dgreaves$(echo .)com \
--cc=elenstev@mesatop$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pasky@ucw$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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