From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix description of alpha in MAINTAINERS
Date: Thu, 13 Jun 2002 12:35:00 -0000 [thread overview]
Message-ID: <20020613193528.GB6124@nevyn.them.org> (raw)
In-Reply-To: <3CC6F636.2030203@cygnus.com>
On Wed, Apr 24, 2002 at 02:15:18PM -0400, Andrew Cagney wrote:
> >On Wed, Apr 24, 2002 at 10:16:29AM +0100, Richard Earnshaw wrote:
> >
> >>> On Tue, Apr 23, 2002 at 11:25:53AM +0100, Richard Earnshaw wrote:
> >>>
> >>> > This probably deserves an entry in NEWS as well.
> >>>
> >>> Like so?
> >>>
> >>> * NEWS: Note multi-arch support for Alpha targets.
> >
> >>
> >>I would have thought so, but that's not something I can approve.
> >
> >
> >I can't find the message any more, but I believe any maintainer is
> >allowed to add to NEWS. If that's true, perhaps it should be mentioned
> >in MAINTAINERS?
>
> Yes, its true (isn't it explictly mentioned?).
Now it is :) Committed.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
2002-06-13 Daniel Jacobowitz <drow@mvista.com>
* MAINTAINERS: Mention NEWS.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.181
diff -u -p -r1.181 MAINTAINERS
--- MAINTAINERS 12 Jun 2002 00:55:35 -0000 1.181
+++ MAINTAINERS 13 Jun 2002 19:33:38 -0000
@@ -350,6 +350,8 @@ Makefile.in, configure* ALL
mmalloc/ ALL Host maintainers
+NEWS ALL
+
sim/ See sim/MAINTAINERS
readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
prev parent reply other threads:[~2002-06-13 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 10:01 Jason R Thorpe
2002-04-23 3:26 ` Richard Earnshaw
2002-04-23 12:55 ` Jason R Thorpe
2002-04-24 2:17 ` Richard Earnshaw
2002-04-24 9:02 ` Daniel Jacobowitz
2002-04-24 11:15 ` Andrew Cagney
2002-06-13 12:35 ` Daniel Jacobowitz [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=20020613193528.GB6124@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.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