From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>,
emacs-devel@gnu.org
Subject: Re: Our use of the "fixed" tag in debbugs
Date: Fri, 08 Oct 2021 17:00:32 +0100 [thread overview]
Message-ID: <874k9r1p7j.fsf@tcd.ie> (raw)
In-Reply-To: <fqy273sew1.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 08 Oct 2021 11:41:21 -0400")
Glenn Morris [2021-10-08 11:41 -0400] wrote:
> "Basil L. Contovounesios" wrote:
>
>> Eli Zaretskii [2021-10-08 14:21 +0300] wrote:
>>
>>> Btw, "close NNN XX.YY" doesn't mark the bug as "done", see
>
> Yes it does.
>
>> But I feel like I've run into a "closed but not done" issue once before,
>> so maybe there's a bug under certain conditions.
>
> I don't know what "closed but not done" really means, but this sounds
> like either:
>
> "forgot to (b)cc the control server" (so not closed at all)
> or
> "closed by forcemerge with an already closed bug" (so closed but no
> new "done" message gets sent out)
I looked earlier but couldn't find the one I was thinking of
unfortunately. My impression is that I closed the bug somehow, received
an email acknowledging that I'd closed it, but on bugs.gnu.org it didn't
say "Done". Perhaps you're right and I misunderstood at the time or am
misremembering.
--
Basil
next prev parent reply other threads:[~2021-10-08 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 17:27 Our use of the "fixed" tag in debbugs Stefan Kangas
2021-10-05 17:52 ` Lars Ingebrigtsen
2021-10-05 17:56 ` Stefan Kangas
2021-10-05 17:57 ` Glenn Morris
2021-10-05 18:12 ` Basil L. Contovounesios
2021-10-05 19:08 ` Eli Zaretskii
2021-10-05 19:44 ` Stefan Kangas
2021-10-05 21:48 ` Stefan Monnier
2021-10-06 7:44 ` Robert Pluim
2021-10-08 11:21 ` Eli Zaretskii
2021-10-08 11:44 ` Basil L. Contovounesios
2021-10-08 15:41 ` Glenn Morris
2021-10-08 16:00 ` Basil L. Contovounesios [this message]
2021-10-08 17:16 ` Stefan Kangas
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=874k9r1p7j.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=stefan@marxist.se \
/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).