From: Michael Albinus <michael.albinus@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: debbugs.el revisited
Date: Sat, 02 Jul 2011 20:03:03 +0200 [thread overview]
Message-ID: <87fwmoef1k.fsf@gmx.de> (raw)
In-Reply-To: <974o348tfp.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 02 Jul 2011 13:48:42 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Lars Magne Ingebrigtsen wrote:
>
>> 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?
>
> I think that's a bad idea. The right number to use in that case would be
> "24.1", ie the first _release_ in which something is fixed. "24.0.50.6",
> or even "24.0.50" is a meaningless version number.
> Obviously you could automatically deduce "24.1" and use that instead,
> but I think passing a version number by default is not a good idea.
> Just give the option to specify a version number when the user thinks
> it's appropriate, and otherwise don't pass one.
I've implemented it by prompting the user; she could change. The default
version number is the same as used by `report-emacs-bug', "24.0.50" this
case.
I see your point, using a _release_ number. I'll change.
Btw, <http://debbugs.gnu.org/server-control.html> documents it as
close bugnumber [ fixed-version ] (deprecated)
What does the "deprecated" means to us?
Best regards, Michael.
next prev parent reply other threads:[~2011-07-02 18:03 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
2011-07-02 13:04 ` Michael Albinus
2011-07-02 17:48 ` Glenn Morris
2011-07-02 18:03 ` Michael Albinus [this message]
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
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=87fwmoef1k.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--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).