Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: cgd@broadcom.com
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [applied patch] update top-level config.sub, config.guess.
Date: Thu, 18 Jul 2002 13:32:00 -0000	[thread overview]
Message-ID: <3D37205A.2010003@ges.redhat.com> (raw)
In-Reply-To: <yov5adoouahh.fsf@broadcom.com>

> retrieving revision 1.17
> diff -u -p -r1.17 MAINTAINERS
> --- MAINTAINERS	7 Apr 2002 19:17:07 -0000	1.17
> +++ MAINTAINERS	18 Jul 2002 18:59:20 -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

Yes (not sure how I missed dejagnu/config.sub).

Andrew



  reply	other threads:[~2002-07-18 20:09 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 [this message]
     [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
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=3D37205A.2010003@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.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