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@xxxxxx> 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@xxxxxx > http://www.tildesoft.com > > > -- Zack Brown -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
