This is the mail archive of the
mailing list for the GCC project.
Re: Lattice Mico32 port
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: Jon Beniston <jon at beniston dot com>
- Cc: Richard Henderson <rth at redhat dot com>, gcc at gcc dot gnu dot org, Joseph Myers <joseph at codesourcery dot com>, sebastien dot bourdeauducq at lekernel dot net
- Date: Tue, 3 Nov 2009 11:52:40 -0500
- Subject: Re: Lattice Mico32 port
- References: <E1Mpjsy-00038a-Hr@fencepost.gnu.org> <007901ca3b00$1c144650$543cd2f0$@com> <Pine.LNX.firstname.lastname@example.org> <00ad01ca3bca$0058e9a0$010abce0$@com> <4ABA5AC5.email@example.com> <004001ca408e$2aaaa2c0$7fffe840$@com> <4AC15C34.firstname.lastname@example.org> <009401ca46b0$440e80b0$cc2b8210$@com> <4ACF7764.email@example.com> <002301ca524c$e8ca13b0$ba5e3b10$@com>
On Wed, Oct 21, 2009 at 7:49 AM, Jon Beniston <firstname.lastname@example.org> 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.