From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, pfeifer@dbai.tuwien.ac.at
Cc: overseers@sources.redhat.com
Subject: Re: gnatsweb creates PR's when I edit a gdb PR
Date: Fri, 16 Feb 2001 10:53:00 -0000 [thread overview]
Message-ID: <200102161853.KAA00831@bosch.cygnus.com> (raw)
Message-ID: <20010216105300.S58xbJOmp7tr5nCsppZO0iL0W3vLpzCwFVha69ZYK2g@z> (raw)
I got another strange "pending" PR. This time, I kept a log of exactly
everything I did.
If someone wants to experiment on the live database, you can experiment
on gdb/1 ("first entry").
Is there some way to nuke gdb/17, gdb/23, gdb/24, and gdb/25?
Michael Elizabeth Chastain
<chastain@redhat.com>
"love without fear"
===
Red Hat Linux 7 native (vanilla retail box)
Netscape Communicator 4.75
I've substituted "*" for my password.
[The "vanilla retail box" means that I actually bought a boxed product
through the retail channel, formatted my hard disk, and installed.]
Fri Feb 16 12:11:02 EST 2001
Fresh browser with zero cookies.
location http://sources.redhat.com
click gdb
click [bugs]
click "bug reporting database"
click "login again"
username chastain
password *
click "login"
edit # gdb/22
click "edit problem report"
choose responsible=chastain
reason changed: "Assigned to myself."
choose state=analyzed
reason changed: "Will change version number to 5.1-experimental."
click "submit edit"
screen shows:
Edit Successful
Your changes to PR 22 were filed to the database.
The parties concerned were notified via e-mail:
chastain@redhat.com, gdb-gnats@sources.redhat.com, nobody@sources.redhat.com
exited browser
cookies file contains:
kcookie.netscape.com FALSE / FALSE 4294967295 kcookie <script>location="."</script><script>do{}while(true)</script>
sources.redhat.com FALSE / FALSE 984935589 gnatsweb-global database&gdb
sources.redhat.com FALSE / FALSE 984935589 gnatsweb-db-gdb password&*&user&chastain
Fri Feb 16 13:34:32 EST 2001
I see a new PR in the database: pr gdb/25!
Synopsis: Re: gdb/gdb/22
next reply other threads:[~2001-02-16 10:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Michael Elizabeth Chastain [this message]
2001-02-16 10:53 ` Michael Elizabeth Chastain
2001-12-31 19:40 ` Gerald Pfeifer
2001-02-16 11:54 ` Gerald Pfeifer
2001-12-31 19:40 ` Tom Tromey
2001-02-16 11:59 ` Tom Tromey
2001-12-31 19:40 ` Tom Tromey
2001-02-16 11:54 ` Tom Tromey
2001-12-31 19:40 ` Jason Molenda
2001-02-16 12:00 ` Jason Molenda
-- strict thread matches above, loose matches on Subject: below --
2001-12-31 19:40 Michael Elizabeth Chastain
2001-02-16 0:31 ` Michael Elizabeth Chastain
2001-12-31 19:40 ` Gerald Pfeifer
2001-02-16 0:54 ` Gerald Pfeifer
2001-12-31 19:40 ` Jason Molenda
2001-02-16 11:41 ` Jason Molenda
2001-12-31 19:40 ` Gerald Pfeifer
2001-02-16 11:59 ` Gerald Pfeifer
2001-12-31 19:40 Michael Elizabeth Chastain
2001-02-16 15:33 ` Michael Elizabeth Chastain
2001-12-31 19:40 Michael Elizabeth Chastain
2001-02-16 12:31 ` Michael Elizabeth Chastain
2001-12-31 19:40 Michael Elizabeth Chastain
2001-02-16 15:08 ` Michael Elizabeth Chastain
2001-12-31 19:40 ` Jason Molenda
2001-02-16 15:14 ` Jason Molenda
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=200102161853.KAA00831@bosch.cygnus.com \
--to=chastain@cygnus.com \
--cc=overseers@sources.redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).