git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Dressel <MichaelTiloDressel@t-online.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] allow '%d' pretty format specifier to show decoration
Date: Wed, 20 Aug 2008 23:05:43 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.1.10.0808202305230.4170@pollux> (raw)
In-Reply-To: <7vzln7phe1.fsf@gitster.siamese.dyndns.org>



On Wed, 20 Aug 2008, Junio C Hamano wrote:

> Michael Dressel <MichaelTiloDressel@t-online.de> writes:
>
>> I use it in a script to extract the log title of commits between certain
>> tags.
>
> "git shortlog"?
>

I use my script to see all the changes (by log titles) between
the commit (prev) I ran the script the last time and the current commit (curr). Now there may be uninteresting tags and some commits may have more
than one tag. Merges made before tag B may introduce commits (say c1) that are 
made before say tag A but with git log prev..curr I may get a list like this

curr (current commit)
.
.
B (latest tag)
A (previous tag)
c1 (commit merged some time between A and B. 
.
.
prev (commit when script was run the last time)


Actually I use "git rev-list prev..curr" to get a list  of commits between
the last time I ran the script and the current head of the branch. Then
I need the git log --decorate only to get _all_ the tags assigned to a 
given commit. Git describe     does not give all the tags, as discussed
earlier. The resulting list of tags assigned to a commit is later
searched for the tag names I'm interested in. And then I use git log
again (git log A..B ) to extract the log titles between every two successive
tags, at this point I may use git shortlog.



Cheers,
Michael

  reply	other threads:[~2008-08-20 21:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 12:25 [BUG?] git log does not decorate when custom format is used MichaelTiloDressel
2008-08-20 17:53 ` Jeff King
2008-08-20 17:55   ` [PATCH 1/2] decorate: allow const objects to be decorated Jeff King
2008-08-20 18:00   ` [PATCH 2/2] allow '%d' pretty format specifier to show decoration Jeff King
2008-08-20 18:32     ` Junio C Hamano
2008-08-20 18:43     ` Johannes Schindelin
2008-08-20 19:01       ` Junio C Hamano
2008-08-20 19:53         ` Johannes Schindelin
2008-09-03 19:36       ` Jeff King
2008-08-20 19:51     ` Michael Dressel
2008-08-20 20:21       ` Junio C Hamano
2008-08-20 21:05         ` Michael Dressel [this message]
2008-08-21  5:02     ` "log --pretty=format:" language Teemu Likonen
2008-08-24 18:30       ` Jakub Narebski

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=alpine.LNX.1.10.0808202305230.4170@pollux \
    --to=michaeltilodressel@t-online.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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;
as well as URLs for NNTP newsgroup(s).