From: Simon Marchi <simark@simark.ca>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdbsupport, gnulib: Regenerate with the maintainer mode
Date: Thu, 5 Jan 2023 11:31:40 -0500 [thread overview]
Message-ID: <12713ca5-0eca-3597-f1da-55c51717489d@simark.ca> (raw)
In-Reply-To: <40efe9e0966b091e53172bcfda026cccf3b320f0.1672889568.git.research_trasio@irq.a4lg.com>
On 1/4/23 22:32, Tsukasa OI via Gdb-patches wrote:
> From: Tsukasa OI <research_trasio@irq.a4lg.com>
>
> Those files have changed by regenerating using the maintainer mode.
> {gdbsupport,gnulib}/Makefile.in changed their copyright year.
> ---
> gdbsupport/Makefile.in | 2 +-
> gnulib/Makefile.in | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdbsupport/Makefile.in b/gdbsupport/Makefile.in
> index 6aadae410316..c4b43c99c3d7 100644
> --- a/gdbsupport/Makefile.in
> +++ b/gdbsupport/Makefile.in
> @@ -15,7 +15,7 @@
> @SET_MAKE@
>
> #
> -# Copyright (C) 2020-2022 Free Software Foundation, Inc.
> +# Copyright (C) 2020-2023 Free Software Foundation, Inc.
> #
> # This file is free software; you can redistribute it and/or modify
> # it under the terms of the GNU General Public License as published by
> diff --git a/gnulib/Makefile.in b/gnulib/Makefile.in
> index 6a2091627d28..8d5bf7f16729 100644
> --- a/gnulib/Makefile.in
> +++ b/gnulib/Makefile.in
> @@ -14,7 +14,7 @@
>
> @SET_MAKE@
>
> -# Copyright (C) 2019-2022 Free Software Foundation, Inc.
> +# Copyright (C) 2019-2023 Free Software Foundation, Inc.
>
> # This file is part of GDB.
>
>
> base-commit: 7cbf35923d31f1f02e69131a9e0f6f065ad8053c
> --
> 2.39.0
>
I pointed out the gdbsupport one to Joel here:
https://inbox.sourceware.org/gdb-patches/ef0fb5c9-dadd-3c9e-b49b-b4ee4598c5a0@simark.ca/
I think we need to make sure the new year procedure is updated to avoid
forgetting it in the future. And our procedure should probably include
gnulib too, since someone needs to do it (either us or the binutils
folks).
Simon
prev parent reply other threads:[~2023-01-05 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 2:02 [PATCH 1/2] gdb, gnulib: Regenerate using " Tsukasa OI
2023-01-04 2:02 ` [PATCH 2/2] sim: " Tsukasa OI
2023-01-04 2:11 ` Mike Frysinger
2023-01-04 8:56 ` [PATCH 1/2] gdb, gnulib: " Tsukasa OI
2023-01-05 3:32 ` [PATCH v2] gdbsupport, gnulib: Regenerate with " Tsukasa OI
2023-01-05 16:31 ` Simon Marchi [this message]
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=12713ca5-0eca-3597-f1da-55c51717489d@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=research_trasio@irq.a4lg.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).