unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: delay archive for "important" bugs
Date: Mon, 13 Jan 2014 21:39:01 +0100	[thread overview]
Message-ID: <87r48bk462.fsf@zigzag.favinet> (raw)
In-Reply-To: <87lhyknecj.fsf@gmx.de> (Michael Albinus's message of "Mon, 13 Jan 2014 15:30:52 +0100")

[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]

() Michael Albinus <michael.albinus@gmx.de>
() Mon, 13 Jan 2014 15:30:52 +0100

   > The bug tracker moves a bug to "archive" state after a month
   > (according to the blurb on the homepage).

   That happens only for closed bugs.

Really?  Earlier today, 15344 was not "closed" AFAICT but anyway, i had
to "unarchive" it to be able to continue its thread (via bug-gnu-emacs).
(A previous mail went to /dev/null.)

Perhaps this is a PEBKAC situation -- i wouldn't be surprised...

   > Is it possible to customize this for Emacs to delay the move (to say,
   > three months) for "important" bugs?

   Why?

If a bug is "important", i think it should be visible longer on the
default "browse" link, reproduced here:

http://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;max-bugs=100;base-order=1;bug-rev=1

(from <http://debbugs.gnu.org/Emacs.html>).  I understand that this is
just a question of presentation; i need to play w/ the form...

Hmm, after playing a bit, i think the timeout value has nothing to do w/
whether or not the bug shows up on the default page, but rather the
‘max-bugs’ parameter, plus the particular mix of current bugs...

OK, never mind.  Sorry for the misplaced angst.

   You could always access the archived bugs as well: [debbugs-gnu]

Cool.  I like debbugs-org, too.

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2014-01-13 20:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 14:03 delay archive for "important" bugs Thien-Thi Nguyen
2014-01-13 14:30 ` Michael Albinus
2014-01-13 20:39   ` Thien-Thi Nguyen [this message]
2014-01-13 21:49     ` Michael Albinus
2014-01-13 21:56       ` Glenn Morris
2014-01-13 22:32       ` Bastien
2014-01-14  3:36         ` Michael Albinus
2014-01-13 22:13     ` Glenn Morris
2014-01-14 10:23       ` Thien-Thi Nguyen
2014-01-14 18:19         ` Glenn Morris
2014-01-14 19:37           ` Thien-Thi Nguyen
2014-01-16  1:28           ` ttn unable to mail to debbugs.gnu.org (was: delay archive for "important" bugs) Joshua Judson Rosen
2014-01-16  2:14             ` ttn unable to mail to debbugs.gnu.org Glenn Morris
2014-01-16 21:14               ` Glenn Morris
2014-01-19  7:28                 ` Thien-Thi Nguyen
2014-01-13 17:04 ` delay archive for "important" bugs Glenn Morris

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=87r48bk462.fsf@zigzag.favinet \
    --to=ttn@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).