From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: New tag(s) for debbugs.gnu.org? [was Re: bug#6174: 23.2; mouse-sel-mode doc is misleading]
Date: Thu, 07 Jul 2011 16:55:39 -0400 [thread overview]
Message-ID: <87box5izec.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <jwvaacp4yr5.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 07 Jul 2011 16:38:03 -0400")
As a general comment, please can we think about changing the subject and
the cc list when starting a new topic. This discussion has nothing to do
with mouse-sel-mode, and isn't appropriate for bug#6174's record.
Stefan Monnier wrote:
> Sounds good, tho IIUC debbugs already has a notion of "pending" as a bug
> state, so maybe we should use another word, such as "postpone".
Not really. As I said, bugs.debian.org has "pending" as a tag, but
debbugs.gnu.org does not. ("pending state" does appear in the search
terminology, but I'm not sure that is relevant.)
> We could use a script to un-postpone all bugs whenever the new branch
> is opened.
I don't see what there is for a script to do. You just want someone to
search for all the bugs tagged "pending" (or whatever) and fix them.
Someone (TM) just has to remember to do that when the time comes.
prev parent reply other threads:[~2011-07-07 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96744EC264DC4E52A46A6834E8BDAD05@us.oracle.com>
[not found] ` <m3oc1cw4nl.fsf@quimbies.gnus.org>
[not found] ` <jwvliweesq5.fsf-monnier+emacs@gnu.org>
[not found] ` <m3y60exmn8.fsf@quimbies.gnus.org>
[not found] ` <8nmxgt37c2.fsf@fencepost.gnu.org>
[not found] ` <m3pqlo96p0.fsf@quimbies.gnus.org>
[not found] ` <44y60cdsyy.fsf@fencepost.gnu.org>
2011-07-06 16:56 ` bug#6174: 23.2; mouse-sel-mode doc is misleading Lars Magne Ingebrigtsen
2011-07-06 20:36 ` Michael Welsh Duggan
2011-07-07 20:38 ` Stefan Monnier
2011-07-07 20:55 ` Glenn Morris [this message]
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=87box5izec.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@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).