From: Enze Li <enze.li@hotmail.com>
To: gdb-patches@sourceware.org
Cc: enze.li@gmx.com, jhb@FreeBSD.org
Subject: Re: [PING][PATCH] gdb: use dynamic year in update-freebsd.sh
Date: Tue, 28 Mar 2023 21:40:47 +0800 [thread overview]
Message-ID: <OS3P286MB2152BC2DD9DAEF635FA8D50AF0889@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <OS3P286MB21528181AF732C6767DB4126F0D19@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM>
Hi all,
Kindly PING for this patch. John has reviewed the patch, but still
needs a global maintainer to take a look at it.
Best Regards,
Enze
On Wed, 2023-02-01 at 21:31 +0800, Enze Li via Gdb-patches wrote:
> When running update-freebsd.sh on FreeBSD, I see the following
> modification in freebsd.xml,
>
> -<!-- Copyright (C) 2009-2023 Free Software Foundation, Inc.
> +<!-- Copyright (C) 2009-2020 Free Software Foundation, Inc.
>
> It means that each time, when we running the update-freebsd.sh on
> FreeBSD, we have to correct the year of copyright manually. So fix
> this
> issue by using dynamic year.
>
> Tested by regenerating freebsd.xml on FreeBSD/amd64.
> ---
> gdb/syscalls/update-freebsd.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/syscalls/update-freebsd.sh b/gdb/syscalls/update-
> freebsd.sh
> index b5b882e921b..ce82564e5c0 100755
> --- a/gdb/syscalls/update-freebsd.sh
> +++ b/gdb/syscalls/update-freebsd.sh
> @@ -33,10 +33,12 @@ if [ $# -ne 1 ]; then
> exit 1
> fi
>
> +year=$(date +%Y)
> +
> cat > freebsd.xml.tmp <<EOF
> <?xml version="1.0"?> <!-- THIS FILE IS GENERATED -*- buffer-read-
> only: t -*- -->
> <!-- vi:set ro: -->
> -<!-- Copyright (C) 2009-2020 Free Software Foundation, Inc.
> +<!-- Copyright (C) 2009-$year Free Software Foundation, Inc.
>
> Copying and distribution of this file, with or without
> modification,
> are permitted in any medium without royalty provided the
> copyright
>
> base-commit: 4788abdec79a937e51ad334b608fa1bd03713112
next prev parent reply other threads:[~2023-03-28 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:31 [PATCH] " Enze Li
2023-02-01 19:44 ` John Baldwin
2023-03-28 13:40 ` Enze Li [this message]
2023-03-28 13:50 ` [PING][PATCH] " Simon Marchi
2023-03-28 14:10 ` Enze Li
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=OS3P286MB2152BC2DD9DAEF635FA8D50AF0889@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM \
--to=enze.li@hotmail.com \
--cc=enze.li@gmx.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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).