public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/45922] New: notification email is not sent when an attachment is added
Date: Wed, 06 Oct 2010 23:35:00 -0000	[thread overview]
Message-ID: <bug-45922-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: notification email is not sent when an attachment is
                    added
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz


When I add an attachment to an existing bugreport, no email is sent. This may
cause the new testcase to old bugport to be ignored, because noone knows about
it.

This is what I see when I attach an attachment to an existing bugreport:


Attachment #21979 to bug 45875 created

    Email sent to:
        dcb314@hotmail.com, jamborm@gcc.gnu.org, hubicka@gcc.gnu.org 
    Excluding:
        gcc-bugs@gcc.gnu.org, unassigned@gcc.gnu.org 


This looks acceptable, but in the case of empty CC list, the situation gets
worse:


Attachment #21980 to bug 45921 created

    Email sent to:
        no one 
    Excluding:
        gcc-bugs@gcc.gnu.org, zsojka@seznam.cz, unassigned@gcc.gnu.org 


There is no gcc dev aware of the new testcase, nor the notification is sent to
the mailing list. The newly attached testcase might be useful if there is no
useful testcase yet (because it is not reduced or the bug was hard to
reproduce).


             reply	other threads:[~2010-10-06 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 23:35 zsojka at seznam dot cz [this message]
2010-10-08 16:48 ` [Bug web/45922] " LpSolit at netscape dot net

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=bug-45922-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).