git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jacob Keller <jacob.keller@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Halil Öztürk" <halilozturk55@gmail.com>,
	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 10:21:39 -0700	[thread overview]
Message-ID: <CA+P7+xpasr7gOYiSsdAyCgh6+D8nYQf9vuEhRna8k7HWMu1Rcg@mail.gmail.com> (raw)
In-Reply-To: <55B0B667.6000103@drmicha.warpmail.net>

On Thu, Jul 23, 2015 at 2:39 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
>
> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Yep, that's pretty much how a build system I've had to use does it.
Sadly, this is quite slow, and I'm not sure if doing it built into the
tag via for-each-ref would be faster? I mean obviously having to look
at each commit is slower than just the tag name, but it might be
faster than parsing through the log process? Though the log output has
the advantage that it only shows you tags "on" a given branch.

Regards,
Jake

  reply	other threads:[~2015-07-23 17:22 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
2015-07-23 17:21       ` Jacob Keller [this message]
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

  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=CA+P7+xpasr7gOYiSsdAyCgh6+D8nYQf9vuEhRna8k7HWMu1Rcg@mail.gmail.com \
    --to=jacob.keller@gmail.com \
    --cc=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.
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).