From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] docs: update copyright date to the year 2025
Date: Fri, 3 Jan 2025 11:43:00 +0000 [thread overview]
Message-ID: <Z3fNRM0SSmYGB_y9@redhat.com> (raw)
In-Reply-To: <20250101080116.1050336-1-anisinha@redhat.com>
On Wed, Jan 01, 2025 at 01:31:16PM +0530, Ani Sinha wrote:
> We are already in January 2025! Update copyright notices.
>
> Cc: peter.maydell@linaro.org
> Cc: qemu-trivial@nongnu.org
> Signed-off-by: Ani Sinha <anisinha@redhat.com>
> ---
> docs/conf.py | 2 +-
> include/qemu/help-texts.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/conf.py b/docs/conf.py
> index 164a8ee8b2..31bb9a3789 100644
> --- a/docs/conf.py
> +++ b/docs/conf.py
> @@ -87,7 +87,7 @@
>
> # General information about the project.
> project = u'QEMU'
> -copyright = u'2024, The QEMU Project Developers'
> +copyright = u'2025, The QEMU Project Developers'
> author = u'The QEMU Project Developers'
How about we make this consistent with the help-texts.h file
by making it cover the range of dates, as stuff that was authored
in 2024 and before , doesn't magically change its copyright date
to 2025, only new contribs get that.
>
> # The version info for the project you're documenting, acts as replacement for
> diff --git a/include/qemu/help-texts.h b/include/qemu/help-texts.h
> index 353ab2ad8b..bc8fab9169 100644
> --- a/include/qemu/help-texts.h
> +++ b/include/qemu/help-texts.h
> @@ -2,7 +2,7 @@
> #define QEMU_HELP_TEXTS_H
>
> /* Copyright string for -version arguments, About dialogs, etc */
> -#define QEMU_COPYRIGHT "Copyright (c) 2003-2024 " \
> +#define QEMU_COPYRIGHT "Copyright (c) 2003-2025 " \
> "Fabrice Bellard and the QEMU Project developers"
>
> /* Bug reporting information for --help arguments, About dialogs, etc */
> --
> 2.45.2
>
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-01-03 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 8:01 [PATCH] docs: update copyright date to the year 2025 Ani Sinha
2025-01-02 6:58 ` Thomas Huth
2025-01-03 11:43 ` Daniel P. Berrangé [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=Z3fNRM0SSmYGB_y9@redhat.com \
--to=berrange@redhat.com \
--cc=anisinha@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.