Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: [PATCH] MAINTAINERS: Update path to readline config.{sub,guess} files
Date: Sun, 23 May 2021 23:32:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2105232311000.31561@angie.orcam.me.uk> (raw)

Complement commit 6999161a2a3b ("Move readline to the readline/readline 
subdirectory") and update the path to readline config.{sub,guess} files 
documented in MAINTAINERS.
---
Hi,

 There is a note at the top of MAINTAINERS asking that ChangeLog entries 
be not made for updates to this file, however I can see they have been.  
What shall I do then?  I take it the change is otherwise obvious.

  Maciej
---
 MAINTAINERS |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

gdb-maintainers-readline-config.diff
Index: binutils-gdb/MAINTAINERS
===================================================================
--- binutils-gdb.orig/MAINTAINERS
+++ binutils-gdb/MAINTAINERS
@@ -27,7 +27,7 @@ cgen/; cgen parts of opcodes/, sim/ & in
 	May need separate opcodes/ or sim/ approval for
 		commits of regenerated files there.
 
-config.guess; config.sub; readline/support/config.{sub,guess}
+config.guess; config.sub; readline/readline/support/config.{sub,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

             reply	other threads:[~2021-05-23 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 21:32 Maciej W. Rozycki [this message]
2021-05-24 13:54 ` Nick Clifton via Gdb-patches
2021-05-24 15:22   ` Tom Tromey
2021-05-24 16:15     ` Maciej W. Rozycki
2021-06-07 13:39 kerenyi&qwertynet hu
2021-06-09 15:36 kerenyi&qwertynet hu
2021-06-15 16:23 Nick Clifton via Gdb-patches

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=alpine.DEB.2.21.2105232311000.31561@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    /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