From: "Zack Brown" <zacharyb@gmail.com>
To: "Kevin Ballard" <kevin@sb.org>
Cc: git@vger.kernel.org
Subject: Re: Associating tags with changelogs
Date: Mon, 5 May 2008 00:20:36 -0400 [thread overview]
Message-ID: <218b69370805042120p533cc100r53d5d96888843273@mail.gmail.com> (raw)
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:
> 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
next prev parent reply other threads:[~2008-05-05 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 3:40 Associating tags with changelogs Zack Brown
2008-05-05 3:56 ` Kevin Ballard
2008-05-05 4:20 ` Zack Brown [this message]
2008-05-05 4:06 ` Shawn O. Pearce
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=218b69370805042120p533cc100r53d5d96888843273@mail.gmail.com \
--to=zacharyb@gmail.com \
--cc=git@vger.kernel.org \
--cc=kevin@sb.org \
/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).