From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, jason@molenda.com
Cc: overseers@sources.redhat.com, pfeifer@dbai.tuwien.ac.at
Subject: Re: gnatsweb creates PR's when I edit a gdb PR
Date: Mon, 31 Dec 2001 19:40:00 -0000 [thread overview]
Message-ID: <200102162030.MAA01146@bosch.cygnus.com> (raw)
> Try "22". Numbers are unique within a single database. I wonder if
> gnatsweb isn't accidentally treating "gdb/22" as the PR number in some
> cases, so when it constructs the Subject line it makes it "Re: gdb/gdb/22".
Ironically, I just finished editing "gdb/22" again. Catch ... 22.
I will try closing out all these bogus "pending" PR's this way:
17 21 23 24 25 26
I don't want to get into "edit-pr" if I can help it.
Michael
WARNING: multiple messages have this Message-ID
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, jason@molenda.com
Cc: overseers@sources.redhat.com, pfeifer@dbai.tuwien.ac.at
Subject: Re: gnatsweb creates PR's when I edit a gdb PR
Date: Fri, 16 Feb 2001 12:31:00 -0000 [thread overview]
Message-ID: <200102162030.MAA01146@bosch.cygnus.com> (raw)
Message-ID: <20010216123100.SlhtBxvBqminfpsPgoZWNhXz7LqTjyVJkAH9PGkUsYc@z> (raw)
> Try "22". Numbers are unique within a single database. I wonder if
> gnatsweb isn't accidentally treating "gdb/22" as the PR number in some
> cases, so when it constructs the Subject line it makes it "Re: gdb/gdb/22".
Ironically, I just finished editing "gdb/22" again. Catch ... 22.
I will try closing out all these bogus "pending" PR's this way:
17 21 23 24 25 26
I don't want to get into "edit-pr" if I can help it.
Michael
next reply other threads:[~2001-12-31 19:40 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 12:31 ` Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
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
2001-12-31 19:40 Michael Elizabeth Chastain
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 ` Jason Molenda
2001-02-16 12:00 ` Jason Molenda
2001-12-31 19:40 ` Tom Tromey
2001-02-16 11:54 ` Tom Tromey
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 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
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=200102162030.MAA01146@bosch.cygnus.com \
--to=chastain@cygnus.com \
--cc=jason@molenda.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).