From: Ian Lance Taylor <iant@google.com>
To: overseers@gcc.gnu.org
Subject: [Rainer Orth] Changing PR to ASSIGNED doesn't assign to me automatically
Date: Fri, 05 Nov 2010 19:56:00 -0000 [thread overview]
Message-ID: <mcrk4krbl3o.fsf@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 18 bytes --]
Forwarding.
Ian
[-- Attachment #2: Type: message/rfc822, Size: 5028 bytes --]
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc@gcc.gnu.org
Subject: Changing PR to ASSIGNED doesn't assign to me automatically
Date: Fri, 05 Nov 2010 20:54:38 +0100
Message-ID: <yddfwvf7dhd.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
I've noticed an annoying change of behaviour in current Bugzilla
compared to the old installation. If I changed a PR to ASSIGNED, it was
automatically assigned to me. Now, the state does change to ASSIGNED
alright, but the PR still remains assigned to unassigned@gcc.gnu.org,
which doesn't seem to make sense to me. Am I doing something wrong
here? If not, it would be extremely helpful to restore the old 2.x
behaviour.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
reply other threads:[~2010-11-05 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mcrk4krbl3o.fsf@google.com \
--to=iant@google.com \
--cc=overseers@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).