1Please feel free to add, edit, delete this file. 2Please do not make ChangeLog entries. 3 4COPYING, COPYING.LIB, README 5 http://gnu.org. 6 7Makefile.*; configure; configure.in; src-release 8 Any global maintainer can approve changes to these 9 files, but they should be aware that they need to 10 be kept in sync with their counterparts in the GCC 11 repository. Also please notify the following of 12 any committed patches: 13 binutils@sources.redhat.com 14 gdb-patches@sources.redhat.com 15 16bfd/; binutils/; gas/; gprof/; ld/; opcodes/; cpu/; BFD's part of include/ 17 binutils: http://sources.redhat.com/binutils/ 18 Patches to binutils@sources.redhat.com. 19 Please notify the following of any interface changes: 20 gdb-patches@sources.redhat.com 21 22cgen/; cgen parts of opcodes/, sim/ & include/ 23 cgen: http://sources.redhat.com/cgen/ 24 Patches to cgen@sources.redhat.com 25 May need separate opcodes/ or sim/ approval for 26 commits of regenerated files there. 27 28config.guess; config.sub; readline/support/config.{sub,guess} 29 config: http://savannah.gnu.org/projects/config 30 Patches to config-patches@gnu.org. 31 Changes need to be done in tandem with the official CONFIG 32 sources or submitted to the master file maintainer and brought 33 in via a merge. When updating any of these files, please be 34 sure to update all of them. 35 Please notify the following of any committed patches: 36 binutils@sources.redhat.com 37 gdb-patches@sources.redhat.com 38 39depcomp 40 Send bug reports and patches to bug-automake@gnu.org. 41 42gdb/; readline/; sim/; GDB's part of include/ 43 GDB: http://www.gnu.org/software/gdb/ 44 Patches to gdb-patches@sources.redhat.com. 45 See also gdb/MAINTAINERS and sim/MAINTAINERS. 46 47include/ 48 See binutils/, gdb/, sid/, gcc/, libiberty/ etc. 49 50intl/; config.rhost; libiberty/; libiberty's part of include/ 51 gcc: http://gcc.gnu.org 52 Changes need to be done in tandem with the official GCC 53 sources or submitted to the master file maintainer and brought 54 in via a merge. Note: approved patches in gcc's libiberty or 55 intl are automatically approved in this libiberty and intl also; 56 feel free to merge them yourself if needed sooner than the next 57 merge. Otherwise, changes are automatically merged, usually 58 within a day. 59 60ltconfig; ltmain.sh; ltcf-*.sh 61 libtool: http://www.gnu.org/software/libtool/ 62 Changes need to be done in tandem with the official LIBTOOL 63 sources or submitted to the master file maintainer and brought 64 in via a merge. 65 66mkinstalldirs; move-if-change 67 autoconf: http://gnu.org 68 Patches to autoconf-patches@gnu.org. 69 Changes need to be done in tandem with the official AUTOCONF 70 sources or submitted to the master file maintainer and brought 71 in via a merge. 72 73symlink-tree 74 gcc: http://gcc.gnu.org 75 See libiberty. 76 77newlib/; libgloss/ 78 http://sources.redhat.com/newlib/ 79 Patches to newlib@sources.redhat.com. 80 81sid/; SID's part of cgen/ 82 sid: http://sources.redhat.com/sid/ 83 Patches to sid@sources.redhat.com 84 85texinfo/texinfo.tex 86 texinfo: http://ftp.gnu.org. 87 Latest version can be found on ftp://ftp.gnu.org and can be 88 imported at any (reasonable) time. 89 Please not use GCC's texinfo. Please do not import texinfo. 90 91tcl/; tix/; itcl/; tk/; libgui/ 92 insight: http://sources.redhat.com/insight/ 93 Contact insight@sources.redhat.com. 94 95winsup/ 96 cygwin: http://sources.redhat.com/cygwin 97 Patches to cygwin-patches@sources.redhat.com. 98 General discussion cygwin@sources.redhat.com. 99 See also winsup/MAINTAINERS. 100 101config-ml.in; makefile.vms; mkdep; setup.com; 102etc/; utils/; 103 Any global maintainer can approve changes to these 104 files and directories. 105 106compile; depcomp; install-sh; missing; ylwrap; 107config/ 108 Any global maintainer can approve changes to these 109 files and directories, but they should be aware 110 that they need to be kept in sync with their 111 counterparts in the GCC repository. 112 113modules file 114 Obviously changes to this file should not go through 115 overseers@sources.redhat.com. If you understand the file 116 format (or can cut-and-paste existing entries), modify it. If 117 it scares you, get someone who does understand it to help you. 118 Be prepared to fix it if you do break it. 119 120/* Local variables: */ 121/* change-log-default-name: "/dev/null" */ 122/* End: */ 123