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