This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libiberty patches
- From: DJ Delorie <dj at redhat dot com>
- To: kenner at vlsi1 dot ultra dot nyu dot edu
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 10 Dec 2001 15:36:38 -0500
- Subject: Re: libiberty patches
- References: <10112101031.AA17237@vlsi1.ultra.nyu.edu>
> What's the procedure for commiting them? I forget if the one in the
> GCC repository is the master. If not, how does it get done?
GCC is the master. Commit to the gcc repository. The rest is
automatic. You may manually merge patches to the src repository if
you don't wish to wait for my semi-auto-merge, such merges are
automatically approved.
Note that libiberty falls within the rules for blanket write priv
maintainers also (i.e. *you* didn't need to wait for my approval,
since you have blanket write privs), although as it is used for more
than just gcc I humbly request a first shot at approving/rejecting
libiberty patches just in case there's some non-gcc reason for doing
things a certain way.