From: Daniel Jacobowitz <drow@false.org>
To: Douglas Evans <dje@google.com>
Cc: gdb@sourceware.org, iant@google.com
Subject: Re: request Write After Approval permission
Date: Mon, 08 Oct 2007 23:21:00 -0000 [thread overview]
Message-ID: <20071008224254.GA8608@caradoc.them.org> (raw)
In-Reply-To: <e394668d0710081454p48fbd075v5d047f49751502f6@mail.gmail.com>
On Mon, Oct 08, 2007 at 02:54:15PM -0700, Douglas Evans wrote:
> Hi. I'd like to get Write After Approval checkin permission. Google
> has the requisite FSF assignment and I've submitted various patches
> over the years. [And I have an account on sourceware already.]
Our usual habit is to set this up the first time you have a patch
that needs to be committed. It's not a big deal either way though.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-08 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 21:54 Douglas Evans
2007-10-08 23:21 ` Daniel Jacobowitz [this message]
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=20071008224254.GA8608@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=iant@google.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