public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: overseers <overseers@sourceware.cygnus.com>
Subject: Added file src/MAINTAINERS
Date: Sun, 02 Apr 2000 18:20:00 -0000	[thread overview]
Message-ID: <38E7F17C.18998C92@cygnus.com> (raw)
Message-ID: <20000402182000.vFKofQbr0GL9xRiytVmgQEXDFIrrp6V1YopdEonO0MA@z> (raw)

FYI,

I've added the attatched top level file.  It _isn't_ part of any
official sources.  Hopefully it answers the ongoing question of what do
I do with my change :-)

Feel free to add, edit, delete or ignore it.  I've not even added it to
modules:src-support at this stage.

	Andrew
Please feel free to add, edit, delete this file.
Please do not make ChangeLog entries.

COPYING, COPYING.LIB, README
	http://gnu.org .

Makefile.in, configure, configure.in
	Please notify the following of any committed patches.
		bfd@sourceware.cygnus.com
		gdb-patches@sourceware.cygnus.com

bfd/, binutils/, gas/, gprof/, ld/, opcodes/ & BFD's part of include/
	binutils: http://sourceware.cygnus.com/binutils/
	Patches to binutils@sourceware.cygnus.com.
	Please notify the following of any interface changes:
		gdb-patches@sourceware.cygnus.com

config.guess, config.sub
	config: http://gnu.org
	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.

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.

ltconfig, ltmain.sh
	libtool: http://gnu.org
	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.

mkinstalldirs, move-if-change, symlink-tree
	autoconf: http://gnu.org
	Change need to be done in tandem with the official AUTOCONF
	sources or submitted to the master file maintainer and brought
	in via a merge.

newlib/, libgloss/
	http://sourceware.cygnus.com/newlib/
	Patches to newlib@sourceware.cygnus.com.

gdb/, mmalloc/, readline/, sim/ & GDB's part of include/
	gdb: http://sourceware.cygnus.com/gdb/
	Patches to gdb-patches@sourceware.cygnus.com.
	See also gdb/MAINTAINERS, sim/MAINTAINERS, mmalloc/MAINTAINERS.

itcl/, tcl/, tix/, tk/, libgui/
	insight: http://sourceware.cygnus.com/insight/
	Contact insight@sourceware.cygnus.com.

winsup/
	cygwin: http://sourceware.cygnus.com/cygwin
	Contact cygwin@sourceware.cygnus.com.
	See also winsup/MAINTAINERS.

expect/, dejagnu/, config-ml.in, mpw-README, mpw-build.in,
mpw-config.in, mpw-configure, mpw-install, setup.com, texinfo/,
missing, makefile.vms, utils/, config/, config.if, makefile.vms,
missing, ylwrap, mkdep, etc/, install-sh, intl/
	?

modules file
	Obviously changes to this file should not go through
	overseers@sourceware.cygnus.com.  If you understand the file
	format (or can cut-and-paste existing entries), modify it. If
	it scares you, get someone who does understand it to help you.
	Be prepared to fix it if you do break it.

/* Local variables: */
/* change-log-default-name: "/dev/null" */
/* End: */

             reply	other threads:[~2000-04-02 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Andrew Cagney [this message]
2000-04-02 18:20 ` Andrew Cagney
2000-12-30  6:08 ` Jim Kingdon
2000-04-02 19:45   ` Jim Kingdon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38E7F17C.18998C92@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=overseers@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).