From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Wu Zhou <woodzltc@cn.ibm.com>, gdb@sources.redhat.com
Subject: Re: can originator close PRs they submitted? -- Re: fortran/1531: segmentation fault for FOTRAN77 arrays (fwd)
Date: Fri, 01 Jul 2005 18:19:00 -0000 [thread overview]
Message-ID: <20050701181911.GA24761@nevyn.them.org> (raw)
In-Reply-To: <42C5820E.1040606@gnu.org>
On Fri, Jul 01, 2005 at 01:49:02PM -0400, Andrew Cagney wrote:
> Wu, any one listed under write-after-approval (which includes you :-)
> can make changes to the bug database. The details of how to do this
> should have been included in the account welcome letter.
He's been doing that - he was asking about the original PR submitter,
not himself. I'm pretty sure the answer is "no", at least for GNATS.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-01 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 2:45 Wu Zhou
2005-06-28 3:52 ` Daniel Jacobowitz
2005-07-01 17:53 ` Andrew Cagney
2005-07-01 18:19 ` Daniel Jacobowitz [this message]
2005-07-06 9:29 ` Wu Zhou
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=20050701181911.GA24761@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=woodzltc@cn.ibm.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