This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug admin/13746] New: auto-annotate bugzilla from git commits
- From: "roland at gnu dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Fri, 24 Feb 2012 18:01:00 +0000
- Subject: [Bug admin/13746] New: auto-annotate bugzilla from git commits
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13746
Bug #: 13746
Summary: auto-annotate bugzilla from git commits
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: admin
AssignedTo: unassigned@sourceware.org
ReportedBy: roland@gnu.org
CC: carlos@systemhalted.org, roland@gnu.org
Classification: Unclassified
We used to have this under CVS, based on the [BZ #nnn] convention in ChangeLog
entries. We should have it again for git.
Jim Meyering is the general expert in sourceware git setup, and may have
suggestions. He is responsible for the current post-receive hook that
sends email, but that appears to be just a copy of a stock contrib script
distributed with git.
I looked at all the other projects' hooks/post-receive files and there
doesn't appear to be any that did anything interesting other than use the
same email-sending script we have now.
The old CVS setup was controlled by these lines in CVSROOT/loginfo:
# -T foo distinguisher for tmp files
# -G glibc bugzilla "product" field
# -m user@dom email recipient
# -D domain email domain sent from
# -U url cvsweb url
# -C glibc cvsweb ?cvsroot=<argument>
# -s %{sVv} magic args
DEFAULT (/usr/sourceware/bin/log_accum_bugzillafied -T glibc -G glibc -C glibc
-D sourceware.org -U "http://sourceware.org/cgi-bin/cvsweb.cgi/"; -m
glibc-cvs@sourceware.org -s %{sVv})
That script can be seen at:
http://sourceware.org/cgi-bin/cvsweb.cgi/infra/bin/log_accum_bugzillafied?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=sourceware
Ian Taylor was the last person to touch it, but I don't know who is the
best person to ask about any details. It appears to work by a combination
of looking at the local database backing bugzilla, and sending formulaic
email to <sourceware-bugzilla@sourceware.org> to make the posts.
I don't really even know any more who to talk to about the bugzilla setup
itself. So I guess the best place for someone to start here would be to
ping both Jim and overseers@sourceware.org about where to go next.
For stock solutions, a quick search found http://www.theoldmonk.net/gitzilla/
but I have no idea whether that's compatible with the sourceware bugzilla
installation or if the maintainers of sourceware bugzilla would want it
installed, or if it can be easily configured to work with the conventions
we use.
https://wiki.mozilla.org/Bugzilla:Addons#Integration_with_Source_Code_Management_utilities
points to a different thing, but via a link to a blog entry on a server
that says (in French) that the server is dead.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.