From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "19070@debbugs.gnu.org" <19070@debbugs.gnu.org>,
"larsi@gnus.org" <larsi@gnus.org>
Subject: bug#19070: 25.0.50; Provide a user option that filters the buffer list for `switch-to-next-buffer'
Date: Thu, 12 May 2022 17:25:33 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488567F76AB1B638224A81DF3CB9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83y1z6of3j.fsf@gnu.org>
> > > Did you look at the change that was actually installed?
> >
> > If communicated in the bug thread then I'd know the
> > answer to the question, and wouldn't need to ask.
> > It wasn't.
>
> People who want answers to those questions are expected to look in
> Git. A URL to do so was posted many times in response to your
> questions like the above.
>
> Please don't expect people here to post information that you can
> easily and trivially find out yourself.
If there were an accurate classification of whether
a bug was actually fixed, versus not fixed (won't
fix), then I wouldn't need to look at anything.
In that case, "fixed" or "wont-fix" would suffice.
Alas, we now get tons and tons of "fixed"/"Done"
for bugs that are not fixed.
If a bug is partly fixed, in the view of the fixer,
then yes, IMHO it behooves the closing email to make
clear to the filer what parts were fixed, i.e., how
much it was and wasn't fixed. That's being honest
and straightforward.
In the case of a doc bug, if the closing email
includes a _link_ to the fixed doc, or if it simply
includes the actual fixed doc textually, then of
course I'll check that result myself. If not, I'll
have to ask questions such as what I asked here.
For a non-doc bug, a clear description of the fix
can suffice. And a _link_ to the resulting code,
in the closing email, can help.
There's nothing odd or abnormal about expecting
specific info about how/whether a bug is "fixed".
And this is all the more important because we get
so many falsely claimed "Done" closures.
next prev parent reply other threads:[~2022-05-12 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 16:38 bug#19070: 25.0.50; Provide a user option that filters the buffer list for `switch-to-next-buffer' Drew Adams
2022-05-12 1:35 ` Lars Ingebrigtsen
2022-05-12 16:02 ` Drew Adams
2022-05-12 16:47 ` Eli Zaretskii
2022-05-12 16:53 ` Drew Adams
2022-05-12 17:06 ` Eli Zaretskii
2022-05-12 17:25 ` Drew Adams [this message]
2022-05-12 17:37 ` Eli Zaretskii
2022-05-12 17:50 ` Drew Adams
2022-05-12 18:14 ` Eli Zaretskii
2022-05-12 21:57 ` Kévin Le Gouguec
2022-05-13 8:14 ` Robert Pluim
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=SJ0PR10MB5488567F76AB1B638224A81DF3CB9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=19070@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).