This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: importing another file into top-level include directory?
On Mon, Jun 23, 2003 at 01:58:42PM -0400, DJ Delorie wrote:
>
> > Are these "libiberty commit rules" explained anywhere? I wasn't
> > aware that these files are treated specially, and I'm wondering what
> > else I might need to know. I don't see anything in either the GCC
> > or Binutils web sites, and I'm not sure where else to look.
>
> in src/MAINTAINERS in binutils:
>
> include/
> See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
>
> libiberty/; libiberty's part of include/
> gcc: http://gcc.gnu.org
> Changes need to be done in tandem with the official GCC
> sources or submitted to the master file maintainer and brought
> in via a merge. Note: approved patches in gcc's libiberty
> are automatically approved in this libiberty also; feel free
> to merge them yourself if needed sooner than the next merge.
> Otherwise, changes are automatically merged, usually within
> a day.
>
>
> ("libiberty's part of include" means any file there common between gcc
> and src)
Would you mind clarifying that in MAINTAINERS? I would have assumed it
meant only files which are part of libiberty, which this wouldn't be.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer