From: David Edelsohn <dje.gcc@gmail.com>
To: Jon Beniston <jon@beniston.com>
Cc: Richard Henderson <rth@redhat.com>,
gcc@gcc.gnu.org, Joseph Myers <joseph@codesourcery.com>,
sebastien.bourdeauducq@lekernel.net
Subject: Re: Lattice Mico32 port
Date: Tue, 03 Nov 2009 16:52:00 -0000 [thread overview]
Message-ID: <303e1d290911030852o7327a398s86bb60981e5138f9@mail.gmail.com> (raw)
In-Reply-To: <002301ca524c$e8ca13b0$ba5e3b10$@com>
On Wed, Oct 21, 2009 at 7:49 AM, Jon Beniston <jon@beniston.com> wrote:
>> The port is ok to check in.
>
> Great - so can I apply it, or does someone else need to?
Until you have write access to the repository, someone else needs to
commit the patch for you.
The GCC community generally likes to see a few examples of patches
(correctness, coding standards) and knowledge about version control
repositories before giving write access.
Thanks, David
next prev parent reply other threads:[~2009-11-03 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 14:29 David Edelsohn
2009-09-21 21:12 ` Jon Beniston
2009-09-22 15:05 ` Joseph S. Myers
2009-09-22 21:17 ` Jon Beniston
2009-09-23 17:29 ` Richard Henderson
2009-09-29 0:58 ` Jon Beniston
2009-09-29 1:12 ` Richard Henderson
2009-10-04 13:28 ` Jon Beniston
2009-10-05 17:27 ` Ian Lance Taylor
2009-10-06 18:11 ` Jon Beniston
2009-10-10 2:25 ` Richard Henderson
2009-10-21 15:46 ` Jon Beniston
2009-11-03 16:52 ` David Edelsohn [this message]
2009-11-09 0:23 ` Sébastien Bourdeauducq
2009-09-29 1:36 ` Richard Henderson
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=303e1d290911030852o7327a398s86bb60981e5138f9@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jon@beniston.com \
--cc=joseph@codesourcery.com \
--cc=rth@redhat.com \
--cc=sebastien.bourdeauducq@lekernel.net \
/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).