From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Junio C Hamano" <gitster@pobox.com>,
"Halil Öztürk" <halilozturk55@gmail.com>
Cc: git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>
Subject: Re: Feature Request: Passing a number as an option to git tags for displaying latest tags
Date: Thu, 23 Jul 2015 11:39:51 +0200 [thread overview]
Message-ID: <55B0B667.6000103@drmicha.warpmail.net> (raw)
In-Reply-To: <xmqq7fpsroc1.fsf@gitster.dls.corp.google.com>
Junio C Hamano venit, vidit, dixit 22.07.2015 21:20:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> The former, sort by "time", is interesting, but you need to define
>> what to do with various corner cases. For example, some people may
>> have one or more of the following desires:
>>
>> * My project did not use tags for a long time, and started using it
>> recently starting from v1.1.0. The first release only said
>> "Frotz version 1.0.0" in its commit log message. I retroactively
>> did "git tag -s -m 'Frotz 1.1.0' v1.1.0" on that commit.
>
> Obviously, I meant "git tag -s -m 'Frotz 1.0.0' v1.0.0" here.
>
>> In such a case, it is likely that I would want the sorting done
>> based on the committer date on the underlying commit, not the
>> tag's tagger date.
>>
>> * When a bug is found, it is customary in my project to add a
>> "break-<something>" tag to the commit that introduces the bug
>> (and "fix-<something>" tag to the commit that fixes it).
>>
>> When I want to find recently discovered breakages, I want the
>> tags whose names match "break-*" sorted by tagger dates, not the
>> underlying commit's committer dates.
>
> Another use case may be one in which older tags are interesting. In
> other words, you need to be able to sort in reverse, too.
>
>> The necessary ordering machinery to do the above already exists in
>> "for-each-ref". There is a GSoC project that works to unify various
>> features spread across "for-each-ref", "branch -l" and "tag -l" and
>> make them available to all of the three.
>
> And the above is still true even with reverse-order use case.
>
While not quite being intended for that purpose,
git log --oneline --decorate --simplify-by-decoration [-n] --tags
(or with a custom format instead of "--oneline --decorate") may come
close to what you want.[*]
Michael
[*] As Linus once described it (iirc): oooh, evil. I like it.
next prev parent reply other threads:[~2015-07-23 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 17:17 Feature Request: Passing a number as an option to git tags for displaying latest tags Halil Öztürk
2015-07-22 18:36 ` Jacob Keller
2015-07-22 18:58 ` Andreas Schwab
2015-07-22 19:17 ` Junio C Hamano
2015-07-22 19:20 ` Junio C Hamano
2015-07-23 9:39 ` Michael J Gruber [this message]
2015-07-23 17:21 ` Jacob Keller
2015-07-23 18:01 ` Junio C Hamano
2015-07-23 18:12 ` Jacob Keller
2015-07-23 18:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B0B667.6000103@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=halilozturk55@gmail.com \
--cc=karthik.188@gmail.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.
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.