From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>
Cc: 1477@debbugs.gnu.org
Subject: bug#1477: 23.0.60; Customize "not marked HIDDEN" is unclear
Date: Sun, 10 Jul 2011 15:25:32 -0700 [thread overview]
Message-ID: <54C36CE4A54340728295DD511061E6B3@us.oracle.com> (raw)
In-Reply-To: <m3sjqdyezs.fsf@quimbies.gnus.org>
> > It should have simply been closed, which records it as a _bug_ that
> > has been _fixed_. It should not have been recorded as `notabug'.
>
> I thought "fixed" was if it was fixed as a result of the bug
> report, and "notabug" was if it turned out (when investigated)
> that the report reported something that wasn't a bug (ever or still).
That would be "not reproducible", I think.
To me, "not reproducible" refers to the time when you try to reproduce it. In
other software you would also be trying to reproduce it using the same version
as the report, but that's another story.
To me, "not a bug" means that you _can_ reproduce the behavior as reported, and
it is the intended intended behavior.
I'm no expert on this. And it's not a big deal - certainly not important for
this bug report. It might be good to know what the designers of this bug system
had in mind, however.
> Perhaps we need a third flag, like
> "probablyabugatthetimeitwasreportedbutnotabugwhensomeonelooked
> atthebugreport"?
We can't really guess what might have been at the time. We can only compare
what we test now with what was reported.
But in a case like this one, we could perhaps believe the OP who tested both
earlier and later, if he says it was fixed. ;-)
> Or perhaps just close it without a flag. Opinions?
Is there a "not reproducible" category? If so, I'd think that would be the
closest in a case like this. Just one, non-expert opinion.
prev parent reply other threads:[~2011-07-10 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 23:32 bug#1477: 23.0.60; Customize "not marked HIDDEN" is unclear Drew Adams
2011-07-10 12:52 ` Lars Magne Ingebrigtsen
2011-07-10 17:17 ` Drew Adams
2011-07-10 21:50 ` Drew Adams
2011-07-10 21:58 ` Lars Magne Ingebrigtsen
2011-07-10 22:21 ` Deniz Dogan
2011-07-10 22:25 ` Drew Adams [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C36CE4A54340728295DD511061E6B3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=1477@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.