From: Junio C Hamano <gitster@pobox.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: "Michael J Gruber" <git@drmicha.warpmail.net>,
"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 11:01:32 -0700 [thread overview]
Message-ID: <xmqqd1zipxc3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CA+P7+xpasr7gOYiSsdAyCgh6+D8nYQf9vuEhRna8k7HWMu1Rcg@mail.gmail.com> (Jacob Keller's message of "Thu, 23 Jul 2015 10:21:39 -0700")
Jacob Keller <jacob.keller@gmail.com> writes:
> 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?
Is the description in "git for-each-ref --help" somehow unreadable?
An example directly producing formatted text. Show the most
recent 3 tagged commits:
#!/bin/sh
git for-each-ref --count=3 --sort='-*authordate' \
--format='From: %(*authorname) %(*authoremail)
Subject: %(*subject)
Date: %(*authordate)
Ref: %(*refname)
%(*body)
' 'refs/tags'
If you only need the name of the ref, you can use a lot simpler
format string, e.g.
git for-each-ref --count=3 --sort='-*authordate' \
--format='%(refname:short)' refs/tags
git for-each-ref --count=3 --sort='-taggerdate' \
--format='%(refname:short)' refs/tags
next prev parent reply other threads:[~2015-07-23 18:01 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
2015-07-23 18:01 ` Junio C Hamano [this message]
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=xmqqd1zipxc3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=halilozturk55@gmail.com \
--cc=jacob.keller@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox