git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Associating tags with changelogs

From
Zack Brown <zacharyb@gmail.com>
Date
May 5, 2008, 04:20 UTC
Message-ID
<218b69370805042120p533cc100r53d5d96888843273@mail.gmail.com>
In-Reply-To
<436ECC5F-0664-4379-8F69-0121AE5F496E@sb.org>

This seems to be working for me. I just call git-describe for each log entry before I enter it into the database.

Thanks! Zack

On Sun, May 4, 2008 at 11:56 PM, Kevin Ballard <kevin@sb.org> wrote:
Show 39 quoted lines
> Sounds like you want git describe --contains.
>
>  -Kevin Ballard
>
>
>
>  On May 4, 2008, at 11:40 PM, Zack Brown wrote:
>
>
> > I'm using git to extract changelog entries into a MySQL database, and
> > I want to be able to associate each changelog with the official
> > release in which it first appears. I can use "git-tag -l" to see a
> > list of the tags, and I can use "git-log tag1..tag2" to view all the
> > changelogs between two tags, but neither of these are exactly what I
> > want.
> >
> > My script keeps track of the most recent changelog entry that it has
> > processed into the MySQL database, so the next time it runs, it picks
> > up from that entry, using "`git-log sha1string.. --pretty=fuller", and
> > inserts only the changelogs since that entry into the database.
> >
> > What I'd like is to still be able to get only the entries since that
> > sha1 string, while somehow identifying the tag of the release
> > encompassing each entry listed in that set. Then when I input the
> > changelog into my database, I can associate it with the proper
> > official release (or -rc candidate).
> >
> > Is there a command to do that? I don't see anything in the man pages for
> it.
> >
>
>  --
>  Kevin Ballard
>  http://kevin.sb.org
>  kevin@sb.org
>  http://www.tildesoft.com
>
>
>
-- 
Zack Brown
Previous: Kevin BallardNext: Shawn O. Pearce
Message 3 of 4 in “Associating tags with changelogs”
  1. Zack BrownMay 5, 2008
  2. Kevin BallardMay 5, 2008
  3. Zack BrownMay 5, 2008
  4. Shawn O. PearceMay 5, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.