From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Zack Brown <zbrown@tumblerings.org>, git@vger.kernel.org
Subject: Re: git/cogito suggestion: tags with descriptions
Date: Wed, 07 Sep 2005 22:10:59 -0400 [thread overview]
Message-ID: <431F9DB3.5090204@gmail.com> (raw)
In-Reply-To: <7vu0gw1htd.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Zack Brown <zbrown@tumblerings.org> writes:
>
>>It would be great if tags also allowed a brief description to go along with
>>them, that would show up in cg-tag-ls. Then I could seek to a tag that's just
>>an easy-to-type version number, and still have an idea of what's significant
>>about that version because of the descriptive text.
>
> Do people crave for 'git tag' showing list of tags with their
> brief descriptions just like 'git branch' does?
Sort of like what gitweb does now?
prev parent reply other threads:[~2005-09-08 2:11 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
2005-09-08 1:14 ` Junio C Hamano
2005-09-08 2:10 ` A Large Angry SCM [this message]
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=431F9DB3.5090204@gmail.com \
--to=gitzilla@gmail.com \
--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 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.