Associating tags with changelogs

Associating tags with changelogs

[Zack Brown]

Hi folks,

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.

Thanks!
Zack

-- 
Zack Brown

Re: Associating tags with changelogs

[Kevin Ballard]

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

Re: Associating tags with changelogs

[Zack Brown]

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:
> 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

Re: Associating tags with changelogs

[Shawn O. Pearce]

Zack Brown <zacharyb@gmail.com> 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. [...]
> 
> 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.
...
> Is there a command to do that? I don't see anything in the man pages for it.

No, not really.  The way to do this is either invoke
`git describe --contains $sha1` for each commit, or to
keep track of it yourself in the script.

The algorithm is really simple, especially if you have something like
Math::BigInt in Perl.  Make a list of all tags, assign a bit to each
tag, make a hash of commits to BigInt (bitset of tags that contain the
commit).

Then run `git rev-list --all --parents --not sha1string` (where
sha1string is the last commit you added to the database) and copy
the bits of each commit onto its parents until the end of input.

Later loop through those commits again.  If a commit's parent has
a color for a tag but the commit doesn't have that tag, then that
tag is the first time the commit appeared in a tag.

-- 
Shawn.