From: Daniel Berlin <dberlin@dberlin.org>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: gcc@gcc.gnu.org
Subject: Re: bug submitters not converted from GNAT to bugzilla
Date: Sun, 25 May 2003 16:30:00 -0000 [thread overview]
Message-ID: <8785E93A-8ECA-11D7-B77D-000A95A34564@dberlin.org> (raw)
In-Reply-To: <16080.31685.469710.946317@gargle.gargle.HOWL>
On Sunday, May 25, 2003, at 04:16 AM, Matthias Klose wrote:
> Daniel Berlin writes:
>>
>> On Saturday, May 24, 2003, at 03:08 AM, Matthias Klose wrote:
>>
>>> When forwarding reports from the Debian BTS to GCC GNATS, I could
>>> explicitely set the submitter (the submitter of the Debian report)
>>> and
>>> the email address (of the Debian bug report). Currently even adding
>>> an
>>> <debian bug number>@bugs.debian.org to a report doesn't work anymore.
>>>
>> Sorry, there are no provisions for external (IE non-bugzilla account
>> holder) cc's.
>> They have to have accounts.
>> Adding external cc support would likely take at least a month, and i'm
>> just not up for it right now.
>
> what is worse,
Sorry, it's not all that bad to begin with.
You implied in private mail that this is somehow a missing feature.
It's not really. GNATS had no email preferences. Bugzilla has per-user
email preferences. External cc's don't mesh well with each user being
able to control what email they receive, since they *aren't* users.
It's not an easy problem. Consider
1. What do you do if they later become a user? Move all the
external-cc's to be regular cc's? This will cause them to be subject
to the email preferences, which might *not* be what the user expects.
2. How does one come up with a consistent UI for adding both "regular"
cc's, and "external" cc's, that doesn't confuse the hell out of people.
3. Do you really think that someone on an external cc isn't going to
ask to be able to have the same type of email preferences users do?
Then what?
> that _all_ the addresses from the GNATS submitter
> fields cannot be found in bugzilla anymore.
Please stop making such blanket statements, it's simply not correct.
> See PR10888 for
> example. In http://bugs.debian.org/193049 in the message
> 20030520215917.15973.qmail@sources.redhat.com,
> bonnaud@irancy.lis.inpg.fr is still CCed, but not present in bugzilla
> anymore.
Because it was in the originator field, and your name is in the from
field. From overrode originator for purposes of choosing who the
reporter was, so it got marked as being from your account, not hers.
Unfortunately, i never added the results of the x-gnats-notify field to
the cc list.
I can remedy this easily.
> I didn't count the affected reports, but this may be ~80 open
> reports, which were forwarded from the Debian archives.
--Dan
next prev parent reply other threads:[~2003-05-25 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 7:57 Adding "foreign" submitters and CC's to bugzilla reports doesn't work Matthias Klose
2003-05-24 15:17 ` Daniel Berlin
2003-05-25 8:51 ` bug submitters not converted from GNAT to bugzilla Matthias Klose
2003-05-25 16:30 ` Daniel Berlin [this message]
2003-05-25 16:53 ` Joseph S. Myers
2003-05-25 19:00 ` Daniel Berlin
2003-05-25 17:02 ` Matthias Klose
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=8785E93A-8ECA-11D7-B77D-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@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).