Re: merging from gcc
Doug Evans <[email protected]>
| Newsgroups | gmane.comp.gdb.devel,gmane.comp.gnu.binutils |
|---|---|
| Message-ID | <CADPb22Qj-voUQ=Jt=qt6Ug9DCezgM8xte6xUJdCeddLhrECOOQ@mail.gmail.com> |
On Fri, Nov 8, 2013 at 11:53 AM, DJ Delorie <[email protected]> wrote: > >> I'm happy to enhance it or just replace it with a link if it's already >> documented elsewhere. > > what we have is in src/MAINTAINERS: > > Makefile.*; configure; configure.ac; src-release > Any global maintainer can approve changes to these > files, but they should be aware that they need to > be kept in sync with their counterparts in the GCC > repository. Also please notify the following of > any committed patches: > [email protected] > [email protected] > > config.guess; config.sub; readline/support/config.{sub,guess} > config: http://savannah.gnu.org/projects/config > Patches to [email protected]. > Changes need to be done in tandem with the official CONFIG > sources or submitted to the master file maintainer and brought > in via a merge. When updating any of these files, please be > sure to update all of them. > Please notify the following of any committed patches: > [email protected] > [email protected] > > include/ > See binutils/, gdb/, sid/, gcc/, libiberty/ etc. > > intl/; config.rhost; libiberty/; libiberty's part of include/; > compile; depcomp; install-sh; missing; ylwrap; config/ > 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 or > intl are automatically approved in this libiberty and intl also; > feel free to merge them yourself if needed sooner than the next > merge. Otherwise, changes are automatically merged, usually > within a day. > > libdecnumber/ > See libiberty. The master copy of this directory is in the GCC > repository. > > > ltconfig; ltmain.sh; ltcf-*.sh > libtool: http://www.gnu.org/software/libtool/ > Changes need to be done in tandem with the official LIBTOOL > sources or submitted to the master file maintainer and brought > in via a merge. I'd be happy if this text were added. I will check it in if there are no objections. I'm happy to change it as desired as well. 2013-11-11 Doug Evans <[email protected]> * MAINTAINERS: Clarify ownership of include. diff --git a/MAINTAINERS b/MAINTAINERS index dd8601b..b09fbc0 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -47,7 +47,10 @@ gdb/; readline/; sim/; GDB's part of include/ See also gdb/MAINTAINERS and sim/MAINTAINERS. include/ - See binutils/, gdb/, sid/, gcc/, libiberty/ etc. + The rule is that if the file exists in the gcc tree + then gcc owns it. Thus you have to look at the gcc tree + to know whether any particular file is owned by gcc. + See also binutils/, gdb/, sid/, gcc/, libiberty/ etc. intl/; config.rhost; libiberty/; libiberty's part of include/ compile; depcomp; install-sh; missing; ylwrap; config/