Re: [PATCH 2/2] allow '%d' pretty format specifier to show decoration
- From
- Michael Dressel <michaeltilodressel@t-online.de>
- Date
- Aug 20, 2008, 21:05 UTC
- Message-ID
- <alpine.LNX.1.10.0808202305230.4170@pollux>
- In-Reply-To
- <7vzln7phe1.fsf@gitster.siamese.dyndns.org>
On Wed, 20 Aug 2008, Junio C Hamano wrote:
Show 7 quoted lines
> 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