public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 4/5] gdb/copyright.py: Remove testsuite/gdb.base/step-line.{c,inp} special handling
Date: Mon, 01 Jan 2018 04:48:00 -0000	[thread overview]
Message-ID: <20180101044801.7201-5-brobecker@adacore.com> (raw)
In-Reply-To: <20180101044801.7201-1-brobecker@adacore.com>

In the past, these files needed to be handled by hand, because
the testcase was sensitive to the length of the header, which was
potentially changing when new copyright years were added to
the copyright header. Now that we simply maintain and update
a range, the length of the copyright header should not change
as a consequence of the update performed by this script, so
special handling of those files is no longer necessary.

gdb/ChangeLog:

        * copyright.py (BY_HAND): Remove gdb/testsuite/gdb.base/step-line.inp
        and gdb/testsuite/gdb.base/step-line.c.
---
 gdb/ChangeLog    | 5 +++++
 gdb/copyright.py | 4 +---
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 27f7c7ffee..96cc88d658 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
 2018-01-01  Joel Brobecker  <brobecker@adacore.com>
 
+	* copyright.py (BY_HAND): Remove gdb/testsuite/gdb.base/step-line.inp
+	and gdb/testsuite/gdb.base/step-line.c.
+
+2018-01-01  Joel Brobecker  <brobecker@adacore.com>
+
 	* copyright.py (main): Dump the contents of
 	MULTIPLE_COPYRIGHT_HEADERS (separately) from BY_HAND,
 	even if BY_HAND is empty.
diff --git a/gdb/copyright.py b/gdb/copyright.py
index bb21b21601..119f69f9e3 100644
--- a/gdb/copyright.py
+++ b/gdb/copyright.py
@@ -200,9 +200,7 @@ EXCLUDE_ALL_LIST = (
 
 # The list of files to update by hand.
 BY_HAND = (
-    # These files are sensitive to line numbering.
-    "gdb/testsuite/gdb.base/step-line.inp",
-    "gdb/testsuite/gdb.base/step-line.c",
+    # Nothing at the moment :-).
 )
 
 # Files containing multiple copyright headers.  This script is only
-- 
2.11.0

  parent reply	other threads:[~2018-01-01  4:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01  4:48 GDB "Start of New Year Procedure" -- 2018 edition Joel Brobecker
2018-01-01  4:48 ` [PATCH 2/5] Update copyright year in version message of GDB, GDBserver and GDBreplay Joel Brobecker
2018-01-01  4:48 ` [PATCH 3/5] gdb/copyright.py: Do not forget to remind about MULTIPLE_COPYRIGHT_HEADERS Joel Brobecker
2018-01-01  4:48 ` Joel Brobecker [this message]
2018-01-01  6:09 ` GDB "Start of New Year Procedure" -- 2018 edition Joel Brobecker
2018-01-02  6:13 ` Sergio Durigan Junior

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=20180101044801.7201-5-brobecker@adacore.com \
    --to=brobecker@adacore.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).