From: Andrew Cagney <ac131313@redhat.com>
To: Ben Elliston <bje@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/maint] Full -Werror for alpha-elf and h8300hms
Date: Sat, 26 Oct 2002 10:37:00 -0000 [thread overview]
Message-ID: <3DBAD2E3.8030403@redhat.com> (raw)
In-Reply-To: <m365vqrp9e.fsf@scooby.brisbane.redhat.com>
>>>>>> "Andrew" == Andrew Cagney <ac131313@redhat.com> writes:
>
>
> Andrew> This tweaks the MAINTAINERS file noteing that the alpha-elf
> Andrew> and h8300hms targets are expected to build without any of
> Andrew> GDB's -W warnings.
>
> I've been noticing that the MAINTAINERS file has been slowly evolving
> into a HACK-RULES file. Is there any chance it could be split into
> two so that their filenames indicate their true contents?
Things to-do-today includes integrate the MAINTAINERS, README and
(nonexistant) INSTALL files into the doco. Interested? :-) The doco
already contains things like coding standards (which I guess can be
thought of as HACK-RULES :-).
Andrew
prev parent reply other threads:[~2002-10-26 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 7:10 Andrew Cagney
2002-10-25 17:57 ` Ben Elliston
2002-10-26 10:37 ` Andrew Cagney [this message]
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=3DBAD2E3.8030403@redhat.com \
--to=ac131313@redhat.com \
--cc=bje@redhat.com \
--cc=gdb-patches@sources.redhat.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