From: Andreas Schwab <schwab@linux-m68k.org>
To: Pedro Alves <palves@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb <gdb@sourceware.org>
Subject: Re: Cleaning out obsolete bugs in bugzilla
Date: Wed, 12 Mar 2014 17:15:00 -0000 [thread overview]
Message-ID: <877g7znxsr.fsf@igel.home> (raw)
In-Reply-To: <53209273.9090407@redhat.com> (Pedro Alves's message of "Wed, 12 Mar 2014 16:59:31 +0000")
Pedro Alves <palves@redhat.com> writes:
> 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?
IMHO a bug that is fixed on mainline should be marked FIXED with the
target milestone set to the version it was fixed in.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2014-03-12 17:15 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
2014-03-31 17:42 ` Doug Evans
2014-03-12 17:15 ` Andreas Schwab [this message]
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=877g7znxsr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=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