This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug admin/13746] auto-annotate bugzilla from git commits
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 15 Oct 2013 15:35:17 +0000
- Subject: [Bug admin/13746] auto-annotate bugzilla from git commits
- Auto-submitted: auto-generated
- References: <bug-13746-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13746
--- Comment #11 from Tom Tromey <tromey at redhat dot com> ---
(In reply to joseph@codesourcery.com from comment #10)
> On Tue, 15 Oct 2013, tromey at redhat dot com wrote:
>
> > * Replace glibc.git/hooks/post-receive with a symlink to
> > /usr/share/doc/git-core/contrib/hooks/post-receive-email
> > This is derived from the same script currently used by glibc.
>
> I don't see such a file on sourceware. There are lots of
> post-receive-email files - which do you mean?
Sorry, I copied the wrong file name.
It is really /sourceware/infra/bin/post-receive-email
> For glibc-cvs mails we show the complete diffs of the commit, but I don't
> think we want the full diffs (which can be very large) to show in Bugzilla
> comments. Can it be configured to show less information in Bugzilla than
> in glibc-cvs?
Yes, from the comments in the file:
# hooks.bugzillashowrev
# Like hooks.showrev, but only used for the bugzilla notification.
# Defaults to hooks.showrev.
You'll want to test this, though, since I don't think I ended up using
this feature for src.git.
> How does this hook identify relevant bugs? In ChangeLog entries in glibc
> we use [BZ #N]; conventions in git logs are less defined, but "bug N",
> "bug #N" and "BZ #N" are common. We would in any case need to inform
> libc-alpha of the patterns to use in git logs, and update the contribution
> / commit checklists accordingly.
It does exactly what log_accum_bugzilla used to do, which is:
while ($log_txt =~
m/[^Aa](?:bug|PR|BZ)\s+\#?\s*(?:[a-z+-]+\/)?(?:\/)?(\d+)(.*)$/si) {
$bug_id = $1;
$log_txt = $2;
Somewhat unreadable I suppose. I didn't edit the regexp when I
pulled out the bugzilla bits into a new script.
--
You are receiving this mail because:
You are on the CC list for the bug.