Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: gdb-patches@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: RFC/PATCH Tweaks to the MAINTAINERS file
Date: Fri, 08 Mar 2002 09:01:00 -0000	[thread overview]
Message-ID: <200203081700.RAA22384@cam-mail2.cambridge.arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]


I'm trying to set up an auto-build script for gdb and I've noted a couple 
of minor problems in the MAINTAINERS file, ok to install?

R.

<date>  Richard Earnshaw  <rearnsha@arm.com>

	* MAINTAINERS: Fix typo in name of gdb warnings option.
	(x86-64): Fix formating so that this can be parsed by awk.



[-- Attachment #2: gdb-maint.patch --]
[-- Type: text/x-patch , Size: 913 bytes --]

Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.159
diff -p -r1.159 MAINTAINERS
*** MAINTAINERS	2002/03/06 09:12:51	1.159
--- MAINTAINERS	2002/03/08 16:56:46
*************** maintainer works with the native maintai
*** 170,176 ****
  
  	w65		Deleted.
  
! 	x86-64		(--target=x86_64-linux-gnu, broken)
  			Maintenance only
  
  	xstormy16	--target=xstormy16-elf ,-Werror
--- 170,176 ----
  
  	w65		Deleted.
  
! 	x86-64		(--target=x86_64-linux-gnu broken)
  			Maintenance only
  
  	xstormy16	--target=xstormy16-elf ,-Werror
*************** The GAWK segment:
*** 204,210 ****
    }'
  
  can be used to generate a full list of --target=
! --enable-gdb-build-warning= pairs.
  
  
  
--- 204,210 ----
    }'
  
  can be used to generate a full list of --target=
! --enable-gdb-build-warnings= pairs.
  
  
  

             reply	other threads:[~2002-03-08 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08  9:01 Richard Earnshaw [this message]
2002-03-08 10:59 ` 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=200203081700.RAA22384@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.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