public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Update copying.awk for _initialize declaration patch
Date: Sun,  2 Jan 2022 19:50:25 +0000 (GMT)	[thread overview]
Message-ID: <20220102195025.01AC73858C2C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5046fddb3aebf6791eb272a369db459ed7bd7a03

commit 5046fddb3aebf6791eb272a369db459ed7bd7a03
Author: Tom Tromey <tom@tromey.com>
Date:   Sun Jan 2 12:16:37 2022 -0700

    Update copying.awk for _initialize declaration patch
    
    Commit 6c265988 ("gdb: add back declarations for _initialize
    functions") modified copying.c, but not copying.awk.  This patch
    updates copying.awk to backport the appropriate fix.  This way, if
    copying.awk is run again, it will create the correct output.
    
    I'm checking this in as obvious.

Diff:
---
 gdb/copying.awk | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gdb/copying.awk b/gdb/copying.awk
index 1cd596a5641..702a6b4338a 100644
--- a/gdb/copying.awk
+++ b/gdb/copying.awk
@@ -50,8 +50,9 @@ NR == 1,/^[ 	]*15\. Disclaimer of Warranty\.[ 	]*$/	{
 END	{
 	  print "}";
 	  print "";
+	  print "void _initialize_copying ();"
 	  print "void"
-	  print "_initialize_copying (void)";
+	  print "_initialize_copying ()";
 	  print "{";
 	  print "  add_cmd (\"copying\", no_set_class, show_copying_command,";
 	  print "	   _(\"Conditions for redistributing copies of GDB.\"),";


                 reply	other threads:[~2022-01-02 19:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220102195025.01AC73858C2C@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).