From: David Taylor <taylor@cygnus.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: Kevin Buettner <kevinb@cygnus.com>, gdb@sources.redhat.com
Subject: Re: GDB GNATS bug tracking database available
Date: Fri, 27 Oct 2000 08:50:00 -0000 [thread overview]
Message-ID: <200010271549.LAA26471@texas.cygnus.com> (raw)
Date: Fri, 27 Oct 2000 14:39:41 +0000
From: Fernando Nasser <fnasser@cygnus.com>
Kevin Buettner wrote:
>
> On Oct 26, 11:10pm, Christopher Faylor wrote:
>
> > I've set up a GNATS database for entering GDB bugs. The easiest way
> > to find it is to go to the gdb web page and follow the BUGS link.
> >
> > http://sources.redhat.com/gdb/
>
> I'm playing around with it now and I'm able to query all of the
> bugs, but when I try to view one of them by clicking on the bug's
> number, I see:
>
> View Problem Report: 12 User: guest
> Database: gdb
> Access: viewconf
> Error: no PRs matched
>
> Is this right?
No, you have to login first. There is an option in the query page
that says "login again". Use that first and you'll get edit priviledges.
So, if you don't want to make any changes, you just want to see more
information than the one line summary, you have to have edit
privileges? That is not what I would have naively expected.
Also, perhaps we should improve the error message a bit -- a message of
"Error: no PRs matched" makes me think that "no PRs matched" rather than
"Sorry, you need edit privileges to do that. Please login again."
next reply other threads:[~2000-10-27 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 8:50 David Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-26 20:10 Christopher Faylor
[not found] ` <cgf@redhat.com>
2000-10-26 21:18 ` Kevin Buettner
2000-10-27 7:39 ` Fernando Nasser
2000-10-27 9:35 ` Christopher Faylor
2000-10-28 4:41 ` Andrew Cagney
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=200010271549.LAA26471@texas.cygnus.com \
--to=taylor@cygnus.com \
--cc=fnasser@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.com \
/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).