public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: <overseers@sources.redhat.com>
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: <Pine.BSF.4.33.0102160948290.55228-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200102160831.AAA21073@bosch.cygnus.com>

On Fri, 16 Feb 2001, Michael Elizabeth Chastain wrote:
> When I edit a PR in gdb gnats, gnats sometimes creates a new PR
> of category "pending".  gdb/17 and gdb/21 are two such PR's.
>
> What are these PR's?  What should I do about them?

Are you, by any chance, changing the synopsis (= subject) of the PRs?
Hmm, no it doesn't seem so.

First I thought it might be the "<<" in the synopsis of one PR, but the
other doesn't have that.

Do you always see this problem, or only for some PRs? If the latter, is
there some common pattern you could identify? (I'm asking because this
does not happen with gnatsweb on gcc.gnu.org, AFAICS, so there must be
something specific going on.)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

WARNING: multiple messages have this Message-ID
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: <overseers@sources.redhat.com>
Subject: Re: gnatsweb creates PR's when I edit a gdb PR
Date: Fri, 16 Feb 2001 00:54:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.33.0102160948290.55228-100000@deneb.dbai.tuwien.ac.at> (raw)
Message-ID: <20010216005400.ku9cD5qQiSbSelixFJuqY6W4gJD6-jm11XnF7DkiBYQ@z> (raw)
In-Reply-To: <200102160831.AAA21073@bosch.cygnus.com>

On Fri, 16 Feb 2001, Michael Elizabeth Chastain wrote:
> When I edit a PR in gdb gnats, gnats sometimes creates a new PR
> of category "pending".  gdb/17 and gdb/21 are two such PR's.
>
> What are these PR's?  What should I do about them?

Are you, by any chance, changing the synopsis (= subject) of the PRs?
Hmm, no it doesn't seem so.

First I thought it might be the "<<" in the synopsis of one PR, but the
other doesn't have that.

Do you always see this problem, or only for some PRs? If the latter, is
there some common pattern you could identify? (I'm asking because this
does not happen with gnatsweb on gcc.gnu.org, AFAICS, so there must be
something specific going on.)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

  parent 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
2001-02-16  0:31 ` Michael Elizabeth Chastain
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 ` Gerald Pfeifer [this message]
2001-02-16  0:54   ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
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
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 10:53 ` Michael Elizabeth Chastain
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
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

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=Pine.BSF.4.33.0102160948290.55228-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=chastain@cygnus.com \
    --cc=overseers@sources.redhat.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).