Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: cgd@broadcom.com
To: ac131313@ges.redhat.com
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [applied patch] update top-level config.sub, config.guess.
Date: Fri, 19 Jul 2002 11:23:00 -0000	[thread overview]
Message-ID: <yov5u1mvfurg.fsf@broadcom.com> (raw)
In-Reply-To: cgd@broadcom.com's message of "Thu, 18 Jul 2002 21:17:28 +0000 (UTC)"

At Thu, 18 Jul 2002 21:17:28 +0000 (UTC), cgd@broadcom.com wrote:
> So, I was going to commit this...  8-)
> 
> the top of MAINTAINERS says:
> 
> Please do not make ChangeLog entries.
> 
> However, there are plenty of (relatively recent) ChangeLog entries
> which refer to MAINTAINERS (2002-04-15, 2002-04-07, 2002-01-16...).
> 
> 
> So, should I or shouldn't I.  8-)

Well, I decided that I'd get this off of my plate, do the update, and
check it in with a ChangeLog since most people had recently done
ChangeLogs when updating MAINTAINERS.

If somebody doesn't like it, they know what to do!  8-)


Checked in as:

2002-07-19  Chris Demetriou  <cgd@broadcom.com>

	* MAINTAINERS: Clarify updates of config.guess and config.sub, and
	add one instance of them which was missed to the list to update.

Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/MAINTAINERS,v
retrieving revision 1.17
diff -u -p -r1.17 MAINTAINERS
--- MAINTAINERS	7 Apr 2002 19:17:07 -0000	1.17
+++ MAINTAINERS	19 Jul 2002 18:14:26 -0000
@@ -21,13 +21,14 @@ cgen/; cgen parts of opcodes/, sim/ & in
 	May need separate opcodes/ or sim/ approval for
 		commits of regenerated files there.
 
-config.guess; config.sub; dejagnu/config.guess;
+config.guess; config.sub; dejagnu/config.guess; dejagnu/config.sub;
 readline/support/config.sub; readline/support/config.guess
 	config: http://savannah.gnu.org/projects/config
 	Patches to config-patches@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.
+	in via a merge.  When updating any of these files, please be
+	sure to update all of them.
 	Please notify the following of any committed patches:
 		binutils@sources.redhat.com
 		gdb-patches@sources.redhat.com




  parent reply	other threads:[~2002-07-19 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 18:36 cgd
2002-07-17 12:37 ` Andrew Cagney
2002-07-18 12:27   ` cgd
2002-07-18 13:32     ` Andrew Cagney
     [not found]       ` <mailpost.1027022991.27023@news-sj1-1>
2002-07-18 14:29         ` cgd
     [not found]           ` <mailpost.1027027047.28864@news-sj1-1>
2002-07-19 11:23             ` cgd [this message]
2002-07-22  6:33           ` Nick Clifton

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=yov5u1mvfurg.fsf@broadcom.com \
    --to=cgd@broadcom.com \
    --cc=ac131313@ges.redhat.com \
    --cc=binutils@sources.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