From: Andrew Cagney <ac131313@cygnus.com>
To: overseers <overseers@sourceware.cygnus.com>
Subject: include src/MAINTAINERS in top lev
Date: Sun, 28 May 2000 21:42:00 -0000 [thread overview]
Message-ID: <3931F520.46B9CF85@cygnus.com> (raw)
Message-ID: <20000528214200.qDPUCfnYGwp5fq-CsVG1ZjQVtucjopV7FymMdU-Gt0g@z> (raw)
FYI,
I intend adding src/MAINTAINERS to the top-level of all the src
modules. Its been a part of the GDB module for sometime. Since its
introduction I've seen a definite switch from:
``Where do I go to get this patch approved?''
to ``FYI, I've committed the attached under the obvious guidelines''
which, I think, has made very ones life a little easier :-)
Andrew
Index: modules
===================================================================
RCS file: /cvs/src/CVSROOT/modules,v
retrieving revision 1.17
diff -p -r1.17 modules
*** modules 2000/04/29 05:48:44 1.17
--- modules 2000/05/29 04:36:43
*************** src-support -a \
*** 29,34 ****
--- 29,35 ----
src/COPYING \
src/COPYING.LIB \
src/ChangeLog \
+ src/MAINTAINERS \
src/Makefile.in \
src/README \
src/config \
*************** naked-gdb -a !src/gdb/gdbtk !src/gdb/tes
*** 111,117 ****
gdb-support -a naked-texinfo naked-bfd naked-opcodes \
naked-readline naked-libiberty naked-mmalloc naked-include \
naked-sim naked-utils src-support naked-intl \
! src/MAINTAINERS src/djunpack.bat
gdb -a naked-gdb gdb-support
--- 112,118 ----
gdb-support -a naked-texinfo naked-bfd naked-opcodes \
naked-readline naked-libiberty naked-mmalloc naked-include \
naked-sim naked-utils src-support naked-intl \
! src/djunpack.bat
gdb -a naked-gdb gdb-support
next reply other threads:[~2000-05-28 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Andrew Cagney [this message]
2000-05-28 21:42 ` Andrew Cagney
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=3931F520.46B9CF85@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).