From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: debbugs.el revisited
Date: Sat, 02 Jul 2011 14:58:07 +0200 [thread overview]
Message-ID: <m3tyb4vnz4.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <c88vshwkkg.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 01 Jul 2011 21:14:07 -0400")
Glenn Morris <rgm@gnu.org> writes:
> BTW, I suggest making debbugs-send-control-message prompt for and pass
> an optional version number when closing bugs. This information is very
> useful, IMO.
The version number is the version number the fix has been applied to?
Then perhaps it could just default to sending over
emacs-version
=> "24.0.50.6"
if the user doesn't override it?
What does the control message for the version number in debbugs look
like?
> Also I don't think adding the "fixed" tags at the same time as you close
> is of any use. The help says:
>
> fixed
> This bug is fixed or worked around, but there's still an issue that
> needs to be resolved
>
> ie fixed is just a weaker version of closed. (It seems like a fairly
> useless tag altogether to me.)
Oh, I thought we wanted to differentiate between (for instance)
"notabug,closed" and "fixed,closed"...
> If someone reopens a bug later on, do they also need to remember to
> remove the "fixed" tag?
Doesn't the same apply to other tags like "notabug"?
> Other commands you might want to add:
> unarchive
> reopen
> merge
> forcemerge
Ok; done.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-02 12:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 17:57 debbugs.el revisited Lars Magne Ingebrigtsen
2011-06-30 19:49 ` Lars Magne Ingebrigtsen
2011-06-30 20:45 ` Michael Albinus
2011-06-30 21:02 ` Chong Yidong
2011-06-30 21:08 ` Lars Magne Ingebrigtsen
2011-06-30 23:26 ` Glenn Morris
2011-06-30 23:34 ` Lars Magne Ingebrigtsen
2011-07-01 2:28 ` Stefan Monnier
2011-07-01 7:12 ` Eli Zaretskii
2011-07-01 8:59 ` Štěpán Němec
2011-07-01 9:25 ` Julien Danjou
2011-07-01 11:16 ` Michael Albinus
2011-07-02 1:14 ` Glenn Morris
2011-07-02 12:58 ` Lars Magne Ingebrigtsen [this message]
2011-07-02 13:04 ` Michael Albinus
2011-07-02 17:48 ` Glenn Morris
2011-07-02 18:03 ` Michael Albinus
2011-07-02 18:08 ` Glenn Morris
2011-07-02 20:14 ` Lars Magne Ingebrigtsen
2011-07-02 20:54 ` Lars Magne Ingebrigtsen
2011-07-02 21:09 ` Christoph Scholtes
2011-07-02 21:15 ` Lars Magne Ingebrigtsen
2011-07-02 22:19 ` Lars Magne Ingebrigtsen
2011-07-02 23:08 ` joakim
2011-07-04 14:47 ` Stefan Monnier
2011-07-03 0:09 ` Christoph Scholtes
2011-07-03 6:34 ` Michael Albinus
2011-07-02 22:30 ` Glenn Morris
2011-07-03 4:48 ` Jason Rumney
2011-07-03 11:07 ` Andreas Schwab
2011-07-02 16:37 ` Michael Albinus
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=m3tyb4vnz4.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.