git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Petr Baudis <pasky@ucw.cz>, greg@kroah.com, git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes
Date: Wed, 20 Apr 2005 16:07:19 -0600	[thread overview]
Message-ID: <4266D297.20506@mesatop.com> (raw)
In-Reply-To: <20050420145419.6412414f.rddunlap@osdl.org>

Randy.Dunlap wrote:
> On Wed, 20 Apr 2005 23:51:18 +0200 Petr Baudis wrote:
> 
> | Dear diary, on Wed, Apr 20, 2005 at 11:19:19PM CEST, I got a letter
> | where Greg KH <greg@kroah.com> told me that...
> | > On Wed, Apr 20, 2005 at 10:56:33PM +0200, Petr Baudis wrote:
> | > >   The short command version will change from 'git' to 'cg', which should
> | > > be shorter to type and free the 'git' command for possible eventual
> | > > entry gate for the git commands (so that they are more
> | > > namespace-friendly, and it might make most sense anyway if we get fully
> | > > libgitized; but this is more of long-term ideas).
> | > 
> | > Hm, but there already is a 'cg' program out there:
> | > 	http://uzix.org/cgvg.html
> | > I use it every day :(
> | > 
> | > How about 'cog' instead?
> | 
> | Grm. Cg is also name of some scary NVidia thing, and cog is GNOME
> | Configurator. CGT are Chimera Grid Tools, but I think we can clash
> | with those - at least *I* wouldn't mind. ;-)
> 
> I'd rather see you go back to 'tig'...
> 
> is there a tig out there?
> 
> ---
> ~Randy

Since I was the one who came up with the "cogito" name, I'll suggest
some alternatives if cogito is unworkable.  This was posted once before,
mostly as a joke, but here goes.

agitato  ag     Since Beethoven's "Moonlight" 3rd mvmt is Presto agitato
                 and very, very fast, just like git.

legit le or lg  Since git is GPLv2, it's now legit.


Steven

  reply	other threads:[~2005-04-20 22:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 20:56 [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Petr Baudis
2005-04-20 21:03 ` Petr Baudis
2005-04-20 21:19 ` Greg KH
2005-04-20 21:51   ` Mike Taht
2005-04-20 21:58     ` Joshua T. Corbin
2005-04-20 21:51   ` Petr Baudis
2005-04-20 21:54     ` Randy.Dunlap
2005-04-20 22:07       ` Steven Cole [this message]
2005-04-20 22:09     ` Linus Torvalds
2005-04-20 22:28       ` Petr Baudis
2005-04-20 23:04         ` Greg KH
2005-04-21  0:14         ` Linus Torvalds
2005-04-21  1:12           ` Linus Torvalds
2005-04-21  3:35             ` Daniel Jacobowitz
2005-04-21  2:45               ` Sean
2005-04-21  4:00               ` Linus Torvalds
2005-04-21  4:22                 ` Dave Jones
2005-04-21  5:08                   ` Junio C Hamano
2005-04-21  4:28                 ` Daniel Jacobowitz
2005-04-21  6:49                   ` Petr Baudis
2005-04-21 14:21                     ` Edgar Toernig
2005-04-21 16:42                       ` Petr Baudis
2005-04-24  0:09                     ` Paul Jackson
2005-04-21  5:14                 ` Randy.Dunlap
2005-04-21  4:27                   ` Sean
2005-04-21  5:29             ` Greg KH
2005-04-24  0:12             ` Paul Jackson
2005-04-21  2:48       ` Matthias Urlichs
2005-04-21 18:15         ` Removing command dispatcher (was Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes) David A. Wheeler
2005-04-21  7:49       ` [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Ingo Molnar
2005-04-25 11:27       ` Andrew Morton
2005-04-21  2:53 ` Bryan Donlan
2005-04-21  7:36   ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4266D297.20506@mesatop.com \
    --to=elenstev@mesatop.com \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=pasky@ucw.cz \
    --cc=rddunlap@osdl.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).