public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug web/46064] New: have to enter a comment to resolve a bug as a duplicate
@ 2010-10-18 12:12 redi at gcc dot gnu.org
  2010-10-18 15:56 ` [Bug web/46064] " pinskia at gcc dot gnu.org
  2010-10-18 16:04 ` redi at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2010-10-18 12:12 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46064

           Summary: have to enter a comment to resolve a bug as a
                    duplicate
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: redi@gcc.gnu.org


Since the upgrade bugzilla requires a comment when resolving a bug as a
duplicate.

Requiring me to type "dup" is pointless, the automatically-inserted "this bug
has been marked as a duplicate..." is self-explanatory


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug web/46064] have to enter a comment to resolve a bug as a duplicate
  2010-10-18 12:12 [Bug web/46064] New: have to enter a comment to resolve a bug as a duplicate redi at gcc dot gnu.org
@ 2010-10-18 15:56 ` pinskia at gcc dot gnu.org
  2010-10-18 16:04 ` redi at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2010-10-18 15:56 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46064

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-10-18 15:56:11 UTC ---
I think this is the right thing to do.  when bugs are marked as dups the
majority of the time, we want an explication.  Because if there was none; the
reporter might open it back up  (even then some of them do but that is a
different issue all together).  I think we should error on the side of cation
here rather than have almost no feedback to the user of GCC.


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug web/46064] have to enter a comment to resolve a bug as a duplicate
  2010-10-18 12:12 [Bug web/46064] New: have to enter a comment to resolve a bug as a duplicate redi at gcc dot gnu.org
  2010-10-18 15:56 ` [Bug web/46064] " pinskia at gcc dot gnu.org
@ 2010-10-18 16:04 ` redi at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2010-10-18 16:04 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46064

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2010-10-18 16:04:21 UTC ---
fair enough


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-10-18 16:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-10-18 12:12 [Bug web/46064] New: have to enter a comment to resolve a bug as a duplicate redi at gcc dot gnu.org
2010-10-18 15:56 ` [Bug web/46064] " pinskia at gcc dot gnu.org
2010-10-18 16:04 ` redi at gcc dot gnu.org

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