From: Duy Nguyen <pclouds@gmail.com>
To: Rahul Bansal <rahul.bansal@rtcamp.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git tag output order is incorrect (IMHO)
Date: Thu, 18 Jul 2013 22:51:55 +0700 [thread overview]
Message-ID: <CACsJy8CpZHTCr0=MkSpfurPW_fyLGN_zd4uSzvBSYbuqH8aXew@mail.gmail.com> (raw)
In-Reply-To: <840FACA0-7E13-41DB-A0F8-124FAB53BFBD@rtcamp.com>
On Thu, Jul 18, 2013 at 10:27 PM, Rahul Bansal <rahul.bansal@rtcamp.com> wrote:
> I am posting here first time, so please excuse me if this is not right place to send something like this.
>
> Please check - http://stackoverflow.com/questions/6091306/can-i-make-git-print-x-y-z-style-tag-names-in-a-sensible-order
>
> And also - https://github.com/gitlabhq/gitlabhq/issues/4565
>
> IMHO "git tag" is expected to show tag-list ordered by versions.
>
> It may be case, that people do not follow same version numbering convention. Most people after x.9.x increment major version (that is why they may not be affected because of this)
>
> Another option like "git tag --date-asc" can be added which will print tags by creation date. (As long as people do not create backdated tag, this will work).
Try
git for-each-ref --sort=committerdate --format='%(refname:short)' refs/tags
--
Duy
next prev parent reply other threads:[~2013-07-18 15:52 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 [this message]
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
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='CACsJy8CpZHTCr0=MkSpfurPW_fyLGN_zd4uSzvBSYbuqH8aXew@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=rahul.bansal@rtcamp.com \
/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).