From: Richard Sandiford <rsandifo@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: brolley@redhat.com
Subject: Write-after-approval access
Date: Tue, 24 Feb 2004 09:10:00 -0000 [thread overview]
Message-ID: <87ekskona1.fsf@redhat.com> (raw)
Not sure whether this is the right way to go about this, so sorry in
advance if I'm breaching etiquette here...
I have some large FR-V sim patches that I'd like to submit. Dave Brolley
seems OK with them in principle. However, it would be more convenient
for both him and me if I had write-after-approval access in order to
check them in. Is it OK to ask for that up-front?
Thanks,
Richard
next reply other threads:[~2004-02-24 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 9:10 Richard Sandiford [this message]
2004-02-24 15:18 ` Andrew Cagney
2004-02-24 15:21 ` Richard Sandiford
2004-02-24 15:29 ` Andrew Cagney
2004-02-25 8:47 ` Richard Sandiford
2004-02-25 18:48 ` Richard Sandiford
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=87ekskona1.fsf@redhat.com \
--to=rsandifo@redhat.com \
--cc=brolley@redhat.com \
--cc=gdb-patches@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