public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Martin dot vGagern at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug web/30584] New: bugzilla: cannot add comments Date: Thu, 25 Jan 2007 10:50:00 -0000 [thread overview] Message-ID: <bug-30584-8905@http.gcc.gnu.org/bugzilla/> (raw) I tried to add a comment to my bug #28686. Being a common user, I could not modify the asignee, that was static text only no entry field. When I comitted my addition, I was asked for my password, and then told: You tried to change the Assignee field from unassigned@gcc.gnu.org to __UNKNOWN__, but only the assignee of the bug, or a sufficiently empowered user may change that field. This effectively prevents me from adding comments to the bug report. Another thing that might be related: When I log in on the home page or through the "Log In" link on any report I get to the home page, and my status is logged in. When I jump from the home page to a specific bug, by entering its number in the form and clicking "Find" or by directly entering its URL, my status is back to not logged in, as I have the "Log In" link in my footer. It would be useful to have this bugzill as a Product as well. gcc is definitely not what this is really about, but I found no better alternative. -- Summary: bugzilla: cannot add comments Product: gcc Version: unknown Status: UNCONFIRMED Severity: major Priority: P3 Component: web AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Martin dot vGagern at gmx dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30584
next reply other threads:[~2007-01-25 10:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-25 10:50 Martin dot vGagern at gmx dot net [this message] 2007-01-25 10:59 ` [Bug web/30584] " rguenth at gcc dot gnu dot org 2007-01-25 11:03 ` Martin dot vGagern at gmx dot net 2007-01-25 11:08 ` Martin dot vGagern at gmx dot net 2007-01-28 3:00 ` manu at gcc dot gnu dot org
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-30584-8905@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: linkBe 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).