From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Rahul Bansal <rahul.bansal@rtcamp.com>
Subject: Re: Git tag output order is incorrect (IMHO)
Date: Fri, 19 Jul 2013 20:22:41 -0400 [thread overview]
Message-ID: <20130720002241.GA22143@sigill.intra.peff.net> (raw)
In-Reply-To: <7vli52uym0.fsf@alter.siamese.dyndns.org>
On Fri, Jul 19, 2013 at 12:40:55PM -0700, Junio C Hamano wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
> > Rahul Bansal <rahul.bansal@rtcamp.com> writes:
> >
> >> IMHO "git tag" is expected to show tag-list ordered by versions.
> >
> > A git tag can be anything, not related to versions at all.
>
> Correct.
>
> But that does not prevent somebody to add "git tag --sort=X" option
> to the command, just like "git for-each-ref" has "--sort=X" option.
A while ago I started on (but did not get very far on) unifying the ref
selection code for for-each-ref, tag, and branch. It would be nice if
they all supported the same set of --contains/--points-at/--merged/--sort,
etc.
I do plan to finish it eventually, but if anyone else feels like picking
it up, I'd be glad to review patches and/or share my work-in-progress as
a starting point.
-Peff
next prev parent reply other threads:[~2013-07-20 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 15:27 Git tag output order is incorrect (IMHO) Rahul Bansal
2013-07-18 15:51 ` Duy Nguyen
2013-07-18 15:56 ` Duy Nguyen
2013-07-18 15:58 ` Rahul Bansal
2013-07-18 15:57 ` Rahul Bansal
2013-07-18 16:14 ` Duy Nguyen
2013-07-18 17:42 ` Andreas Schwab
2013-07-19 19:40 ` Junio C Hamano
2013-07-20 0:22 ` Jeff King [this message]
2013-08-20 15:12 ` Antoine Pelisse
2013-09-08 8:03 ` Jeff King
2013-10-16 17:56 ` Jeff King
2013-10-16 18:06 ` Antoine Pelisse
2013-09-08 22:49 ` Felipe Contreras
2013-09-11 13:42 ` Phil Hord
2013-09-11 17:54 ` Junio C Hamano
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=20130720002241.GA22143@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rahul.bansal@rtcamp.com \
--cc=schwab@linux-m68k.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).