All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git <git@vger.kernel.org>
Subject: Re: Joining cg-*-id
Date: Mon, 19 Sep 2005 18:30:21 -0400	[thread overview]
Message-ID: <1127169021.26772.58.camel@dv> (raw)
In-Reply-To: <20050919215608.GA13845@pasky.or.cz>

Hello, Petr!

Thanks for quick replies.  I'm replying to both your messages.

On Mon, 2005-09-19 at 23:56 +0200, Petr Baudis wrote:
> Dear diary, on Mon, Sep 19, 2005 at 11:40:49PM CEST, I got a letter
> where Pavel Roskin <proski@gnu.org> told me that...
> > Hello!
> 
> Hello,
> 
> > I believe Cogito should keep the command list short.  When the *-id
> > utilities got the cg-prefix, the list became longer by 3 commands.
> 
> well, those commands are semi-public, actually. E.g. cg-help does not
> list them.

But cg-<TAB><TAB> does.

> > What if we join cg-commit-id, cg-parent-id and cg-tree-id into one cg-id
> > (or cg-admin-id) utility?  It would work like cg-commit-id in absence of
> > switches, -p would make it work like cg-parent-id, and -t would make it
> > cg-tree-id.
> 
> Perhaps cg-object-id? I'm not principially opposed to that, but I don't
> see much value in it either. Perhaps if this would come along with
> the usage of git-rev-parse (see below)...

The value is having one command, one manpage and one place to fix little
bugs and add more functionality.  Potentially, cg-Xnormid could be
incorporated into that script, so bash wouldn't have to open one more
file.

> > Alternatively, this functionality should go to git.  It's low-level
> > enough to be there.
> 
> There is git-rev-parse, but it is not as powerful (cannot take dates and
> sha1 completion does not work when listing parents) - OTOH it can
> complete sha1 ids even inside packs, which is really useful. Still, IMHO
> its usage is awful, so it'd take place for cg-Xnormid, but we would
> still keep the *-id frontends (which would also handle the dates).

I see.  I guess time for git is just as abstract as phases of the moon -
nobody would goes crazy when they repeat.

Please don't apply my patch yet - I forgot to document the optional
argument.  I'll try to make cg-object-id now.

-- 
Regards,
Pavel Roskin

  parent reply	other threads:[~2005-09-19 22:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 21:40 Joining cg-*-id Pavel Roskin
2005-09-19 21:56 ` Petr Baudis
2005-09-19 22:16   ` Linus Torvalds
2005-09-19 22:54     ` Petr Baudis
2005-09-20  0:50       ` Linus Torvalds
2005-09-20 13:57         ` Petr Baudis
2005-09-20 14:53           ` Linus Torvalds
2005-09-20 15:07             ` Petr Baudis
2005-09-20 16:54               ` Linus Torvalds
2005-09-20 19:34                 ` Linus Torvalds
2005-09-21 10:35                   ` Paul Mackerras
2005-09-21 14:51                     ` Linus Torvalds
2005-09-21 21:19                       ` Paul Mackerras
2005-09-21  8:50                 ` Petr Baudis
2005-09-20 15:13             ` Matthias Urlichs
2005-09-20  5:52     ` Junio C Hamano
2005-09-20 10:11       ` Matthias Urlichs
2005-09-20 12:32         ` Paul Mackerras
2005-09-19 22:30   ` Pavel Roskin [this message]
2005-09-19 22:58     ` Petr Baudis
2005-09-20  0:19       ` Pavel Roskin
2005-09-20  0:26         ` 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=1127169021.26772.58.camel@dv \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.