From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Fabian Ezequiel Gallina <galli.87@gmail.com>
Subject: Re: Diff emails to debbugs?
Date: Mon, 31 Dec 2012 15:02:35 +0100 [thread overview]
Message-ID: <m37gnys4jo.fsf@stories.gnus.org> (raw)
In-Reply-To: <yxr4m8d9zm.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 29 Dec 2012 12:49:33 -0500")
Glenn Morris <rgm@gnu.org> writes:
> Parsing the commit message sounds like too much work. Just check for a
> --fixes debbugs:123 entry, and if there is one, cc the commit to
> 123@debbugs with some short explanatory note.
Parsing the commit messages is what I did at work to tie the VC and the
bug tracker together. There we use magical strings in the commit
messages to control the bug tracker. So we say "bug 123 fixed" and
stuff. If there isn't recognised keyword after the bug report number,
the patch only refers to the bug (and the diff gets filed with it), but
it doesn't change the status.
An equivalent thing for Emacs would be to look for strings like
"bug#123 done 24.4". The extra nice thing about this is that you can
refer to many bug reports at once. Just say "(bug#123, bug#124 done)"
to have the diff go out to both the 123 and 124 bug reports, and close
the 124 bug report.
This might be over-engineering things, though. And at the same time
under-engineering, since it relies on "magical strings". :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2012-12-31 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 12:08 Diff emails to debbugs? Lars Ingebrigtsen
2012-12-28 19:21 ` Glenn Morris
2012-12-28 23:20 ` Lars Ingebrigtsen
2012-12-29 0:29 ` Glenn Morris
2012-12-29 7:06 ` Stefan Monnier
2012-12-29 9:38 ` Fabian Ezequiel Gallina
2012-12-29 17:49 ` Glenn Morris
2012-12-31 14:02 ` Lars Magne Ingebrigtsen [this message]
2012-12-29 16:29 ` Stephen J. Turnbull
2012-12-29 16:35 ` handling partially fixed bugs [was: Diff emails to debbugs?] Drew Adams
2012-12-29 22:10 ` Xue Fuqiao
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37gnys4jo.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=galli.87@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).