unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 9445@debbugs.gnu.org, larsi@gnus.org, stephen.berman@gmx.net,
	24842@debbugs.gnu.org
Subject: bug#24842: [External] : Re: bug#24842: 24.5; `help-make-xrefs': False link-type determinations
Date: Tue, 15 Feb 2022 21:33:35 +0200	[thread overview]
Message-ID: <83pmnn3oxc.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488264244CE7137679963ECF3349@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Tue, 15 Feb 2022 19:22:00 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> CC: "larsi@gnus.org" <larsi@gnus.org>,
>         "stephen.berman@gmx.net"
> 	<stephen.berman@gmx.net>,
>         "9445@debbugs.gnu.org" <9445@debbugs.gnu.org>,
>         "24842@debbugs.gnu.org" <24842@debbugs.gnu.org>
> Date: Tue, 15 Feb 2022 19:22:00 +0000
> Accept-Language: en-US
> 
> > > The priority shouldn't be to close bugs.  It
> > > should be to report bugs, so they can perhaps
> > > be fixed by someone who has the interest and
> > > energy.
> > 
> > It makes no sense to keep bugs open for years without anyone picking
> > up the gauntlet.  After so many years it is quite reasonable to assume
> > that no one is interested enough to work on this.
> 
> And the reason is?  No reason given.

I just gave it, above.

> Just what is the cost of leaving confirmed bugs
> open?

It's a cost to the project maintenance to have open bugs that no one
works on.

> Just what is the benefit of closing them
> (apart perhaps from showing fewer in a report)?

The benefit is to have a manageable number of bugs that we really want
to fix.

> "It makes no sense" and "it is quite reasonable",
> themselves make little sense

Perhaps for you.  But this is not your call and not your
responsibility.





  reply	other threads:[~2022-02-15 19:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 23:00 bug#24842: 24.5; `help-make-xrefs': False link-type determinations Drew Adams
2016-10-31 23:55 ` npostavs
2016-11-01  4:35   ` Drew Adams
2016-11-01 15:20     ` Eli Zaretskii
2016-11-01 15:34       ` Noam Postavsky
2016-11-01 16:16         ` Eli Zaretskii
     [not found]     ` <<83wpgnns4x.fsf@gnu.org>
2016-11-01 16:15       ` Drew Adams
2016-11-01 16:25         ` Eli Zaretskii
     [not found]       ` <<CAM-tV-_+-Ewzh_vMpi65cc5ukD+T+WHNPGk0dooqQCaJAvmTaQ@mail.gmail.com>
     [not found]         ` <<83r36vnpjw.fsf@gnu.org>
2016-11-01 16:29           ` Drew Adams
2016-11-01 16:50             ` Eli Zaretskii
2017-02-05 19:27 ` Drew Adams
2018-01-01 21:20   ` Drew Adams
2021-09-07 18:00 ` bug#24842: bug#9445: 24.0.50; `help-make-xrefs' has bad logic Lars Ingebrigtsen
2021-09-07 19:24   ` bug#24842: [External] : " Drew Adams
2021-09-07 19:28     ` Lars Ingebrigtsen
2021-09-07 19:44   ` bug#9445: bug#24842: " Stephen Berman
2021-09-07 19:55     ` Lars Ingebrigtsen
2022-02-15 10:43       ` bug#24842: 24.5; `help-make-xrefs': False link-type determinations Lars Ingebrigtsen
2022-02-15 16:58         ` bug#24842: [External] : " Drew Adams
2022-02-15 19:12           ` Eli Zaretskii
2022-02-15 19:22             ` Drew Adams
2022-02-15 19:33               ` Eli Zaretskii [this message]
2021-09-07 20:13     ` bug#24842: [External] : Re: bug#24842: bug#9445: 24.0.50; `help-make-xrefs' has bad logic Drew Adams
     [not found] <<919e40a4-f6c4-492d-b50f-b0671e13cb60@default>
     [not found] ` <<878tt4qdjq.fsf@users.sourceforge.net>

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=83pmnn3oxc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24842@debbugs.gnu.org \
    --cc=9445@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    --cc=stephen.berman@gmx.net \
    /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).