Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Cleaning out obsolete bugs in bugzilla
Date: Wed, 12 Mar 2014 17:10:00 -0000	[thread overview]
Message-ID: <CADPb22Ra_37oHUWfx51pPuScSt3bv5+wjLDejS_zxpsER+Waaw@mail.gmail.com> (raw)
In-Reply-To: <53209273.9090407@redhat.com>

On Wed, Mar 12, 2014 at 9:59 AM, Pedro Alves <palves@redhat.com> wrote:
> On 03/12/2014 04:41 PM, Doug Evans wrote:
>> Hi.  I'll conclude from this that there is no disagreement with
>> closing such obsolete bugs as WONTFIX is ok.
>
> In this case I confirmed mainline builds, so it wasn't exactly
> the sort of "close just because it's old" thing.  But yeah.
> Old build bugs are fine with me to close.
>
> In this case I went with WONTFIX as meaning "Won't fix in
> the 6.3 branch."  But as I confirmed it works on mainline,
> we could go with FIXED too.  It's all the same in the end,
> but maybe FIXED is kinder to the original reporter?

fwiw, I'd hate for these discussions to drag on beyond two emails per
bug in the general case.  There's just too much else to do, and too
many such bugs to deal with.
Thus a high order bit here for me is to find a non-disagreeable way to
streamline the process (and document it so that it can stay
streamlined).

"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.  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.


  reply	other threads:[~2014-03-12 17:10 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 [this message]
2014-03-12 17:24       ` Pedro Alves
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=CADPb22Ra_37oHUWfx51pPuScSt3bv5+wjLDejS_zxpsER+Waaw@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    /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