From: Pavel Roskin Date: Mon, 19 Sep 2005 22:30:21 GMT Subject: Re: Joining cg-*-id Message-ID: <1127169021.26772.58.camel@dv> 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 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- 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