From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Cleaning out obsolete bugs in bugzilla
Date: Wed, 12 Mar 2014 17:24:00 -0000 [thread overview]
Message-ID: <5320982C.2060308@redhat.com> (raw)
In-Reply-To: <CADPb22Ra_37oHUWfx51pPuScSt3bv5+wjLDejS_zxpsER+Waaw@mail.gmail.com>
On 03/12/2014 05:10 PM, Doug Evans wrote:
> "WONTFIX" could come across with an unintended connotation alright,
> but I have no current data to assign a probability to it happening.
> At the moment it's just gut feeling, which is why I think there's
> benefit to something else that doesn't require much, if any,
> discussion, like OBSOLETE.
I think OBSOLETE is a good idea.
> But I don't have a strong opinion on the
> ultimate choice. If people have a strong opinion on not inventing
> anything new, fine by me, let's go with WONTFIX until we have real
> data that it can be a problem.
--
Pedro Alves
next prev parent reply other threads:[~2014-03-12 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 17:58 Doug Evans
2014-03-12 16:41 ` Doug Evans
2014-03-12 16:59 ` Pedro Alves
2014-03-12 17:10 ` Doug Evans
2014-03-12 17:24 ` Pedro Alves [this message]
2014-03-31 17:42 ` Doug Evans
2014-03-12 17:15 ` Andreas Schwab
2014-03-12 17:22 ` Pedro Alves
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=5320982C.2060308@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox