unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: Our use of the "fixed" tag in debbugs
Date: Fri, 08 Oct 2021 14:21:41 +0300	[thread overview]
Message-ID: <83zgrjyd6i.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmakuz1NpiA5p+9JgM2ZmYxPFZuS7vXihVFQHvzK0_-Ew@mail.gmail.com> (message from Stefan Kangas on Tue, 5 Oct 2021 13:27:04 -0400)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 5 Oct 2021 13:27:04 -0400
> 
> We currently use the debbugs "fixed" tag almost exclusively in this way:
> 
>     tags NNN fixed
>     close NNN 29.1
>     thanks
> 
> This is fine by me, no change needed here.  There is a slight
> duplication in that we say that it's fixed twice, but that's minor.

Btw, "close NNN XX.YY" doesn't mark the bug as "done", see
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51029#8 as one example.
This is a problem, because the fact the bug was closed isn't visible
when looking at the first screen of what the browser shows when you
display the bug.

So I think using "close" instead of NNN-done@debbugs.gnu.org should be
discouraged.



  parent reply	other threads:[~2021-10-08 11:21 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 [this message]
2021-10-08 11:44   ` Basil L. Contovounesios
2021-10-08 15:41     ` Glenn Morris
2021-10-08 16:00       ` Basil L. Contovounesios
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=83zgrjyd6i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).