From: Petr Baudis <pasky@suse.cz>
To: Zack Brown <zbrown@tumblerings.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: git/cogito suggestion: tags with descriptions
Date: Sat, 8 Apr 2006 04:35:59 +0200 [thread overview]
Message-ID: <20060408023559.GS27689@pasky.or.cz> (raw)
In-Reply-To: <20050912010051.GJ15630@pasky.or.cz>
Dear diary, on Mon, Sep 12, 2005 at 03:00:51AM CEST, I got a letter
where Petr Baudis <pasky@suse.cz> said that...
> Dear diary, on Mon, Sep 05, 2005 at 11:24:31PM CEST, I got a letter
> where Zack Brown <zbrown@tumblerings.org> told me that...
> > I'm not sure. I'm not as familiar with the low-level git commands as I am with
> > cogito. But cogito has a -d option for giving a tag description. I guess what
> > would be closest to what I was thinking about would be this:
> >
> > $ cg-tag -d "First draft, everything in place." 0.3 7540e503b9b9c1b03e44ee7fd700c844b2a02224
> > $ cg-tag-ls
> > 0.1 Initial idea complete f953b71b21a0bea682c2bed91362f2dce2cc204f
> > 0.3 First draft, everything in place. 7540e503b9b9c1b03e44ee7fd700c844b2a02224
> > $
> >
> > or something like that. Currently when I do the above cg-tag command,
> > a subsequent cg-tag-ls gives just:
> >
> > $ cg-tag-ls
> > 0.1 f953b71b21a0bea682c2bed91362f2dce2cc204f
> > 0.3 7540e503b9b9c1b03e44ee7fd700c844b2a02224
> >
> > In fact, I probably wouldn't even be interested in seeing the actual hash key
> > unless I gave a special flag, maybe -f (for "full"):
> >
> > $ cg-tag-ls
> > 0.1 Initial idea complete
> > 0.3 First draft, everything in place.
> > $ cg-tag-ls -f
> > 0.1 Initial idea complete f953b71b21a0bea682c2bed91362f2dce2cc204f
> > 0.3 First draft, everything in place. 7540e503b9b9c1b03e44ee7fd700c844b2a02224
>
> That's a nice idea (except that I'd prefer -l). I'll implement this
> after cogito-0.14.
So, I did. ;-) (In the master branch now.) The format is slightly
different from the proposed one:
S cogito-0.16rc2 7766e3ba0664
S cogito-0.17 51392f2dd82a Poetic cogito-0.17.
S cogito-0.17rc1 7cb4d8972d5b Behold, cogito-0.17rc1! Plenty new features and cool stuff.
% cogito-0.8 f9f0459b5b39
% cogito-0.9 cc5517b4ea41
test 05862786175d
Object IDs are still shown, but abbreviated so they shouldn't get in the
way too much; the full first line is shown in the list output,
untrimmed. The initial flag column denotes signed tags by 'S', "direct
tags" (not pointing to a tag object) by '%' and broken tags by '!'.
P.S.: Also, cg-tag received a lot of improvements in the last two days.
Now features the same cool editor as cg-commit (but only if ran with
-e), -d was renamed to -m (but will stay aliased for quite some time),
cg-tag now also accepts multiple -m options for creating multi-paragraph
descriptions from the commandline, and bunch of other minor stuff was
implemented.
Thanks for the idea,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time. I think
I have forgotten this before.
next prev parent reply other threads:[~2006-04-08 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 18:45 git/cogito suggestion: tags with descriptions Zack Brown
2005-09-05 19:01 ` Junio C Hamano
2005-09-05 21:24 ` Zack Brown
2005-09-12 1:00 ` Petr Baudis
2006-04-08 2:35 ` Petr Baudis [this message]
2005-09-08 1:14 ` Junio C Hamano
2005-09-08 2:10 ` A Large Angry SCM
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=20060408023559.GS27689@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=zbrown@tumblerings.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.
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).