unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Hyatt <ahyatt@gmail.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Nikolaus Rath <Nikolaus@rath.org>,
	emacs-devel@gnu.org, Drew Adams <drew.adams@oracle.com>,
	Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: Basic questions about the triage process
Date: Fri, 08 Jan 2016 22:47:54 -0500	[thread overview]
Message-ID: <m2twmno1lh.fsf@gmail.com> (raw)
In-Reply-To: <m3oacx13m6.fsf@gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 07 Jan 2016 22:28:17 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>> Is there a "pending-closure" tag, that can be used to help the clean up?
>> Then one person could send the "I think this is outdated now" email, and
>> another close it later.
>
> That's basically "moreinfo".

I've been using the "unreproducible" tag as just this sort of tag - it
means that it can't be reproduced at least by me, and if no one can
reproduce it within a few weeks, it should be turned into
"doneunreproducible".  I've detailed this process in the
admin/notes/triage file (which I'll soon rename to admin/notes/bug-triage).



  reply	other threads:[~2016-01-09  3:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28  5:39 Basic questions about the triage process Andrew Hyatt
2015-12-28  8:58 ` Michael Albinus
2015-12-28 16:25   ` Andrew Hyatt
2015-12-28 17:35     ` Michael Albinus
2015-12-28 20:24 ` John Wiegley
2015-12-29  5:40   ` Andrew Hyatt
2015-12-29 17:12     ` Eli Zaretskii
2015-12-30  0:22       ` Andrew Hyatt
2015-12-30 17:21         ` Eli Zaretskii
2015-12-31  1:19           ` Noam Postavsky
2015-12-31  3:38             ` Eli Zaretskii
2015-12-31  9:06               ` Michael Albinus
2015-12-31 13:49                 ` Eli Zaretskii
2015-12-31 13:57                   ` Michael Albinus
2016-01-07 21:04     ` Phillip Lord
2016-01-07 22:05       ` Andy Moreton
2016-01-07 22:40         ` Phillip Lord
2016-01-09  3:46           ` Andrew Hyatt
2015-12-28 23:55 ` Xue Fuqiao
2015-12-29  0:38   ` Andrew Hyatt
2015-12-29  0:50     ` Lars Ingebrigtsen
2015-12-29  0:59       ` Andrew Hyatt
2015-12-29  1:07         ` Lars Ingebrigtsen
2015-12-29  1:21           ` John Wiegley
2015-12-29  1:50             ` Drew Adams
2016-01-02 21:37               ` Marcin Borkowski
2016-02-15 20:04                 ` Marcin Borkowski
2015-12-29  6:46             ` CHENG Gao
2015-12-29 15:50               ` Eli Zaretskii
2015-12-29 17:03         ` Nikolaus Rath
2015-12-29 17:16           ` John Wiegley
2015-12-29 17:50           ` Drew Adams
2015-12-29 23:36             ` Andrew Hyatt
2016-01-07 21:09               ` Phillip Lord
2016-01-07 21:28                 ` Lars Magne Ingebrigtsen
2016-01-09  3:47                   ` Andrew Hyatt [this message]
2016-01-09 20:56                     ` John Wiegley

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=m2twmno1lh.fsf@gmail.com \
    --to=ahyatt@gmail.com \
    --cc=Nikolaus@rath.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=phillip.lord@russet.org.uk \
    /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).