From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] docs: update copyright years
Date: Wed, 02 Oct 2024 11:22:37 +0200 [thread overview]
Message-ID: <D4L7L9VPFO42.1NNKLUQRKV45C@proxmox.com> (raw)
In-Reply-To: <20240927155812.1754476-1-c.heiss@proxmox.com>
On Fri Sep 27, 2024 at 5:58 PM CEST, Christoph Heiss wrote:
> It's already 2024 for quite some time now.
>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> docs/conf.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/conf.py b/docs/conf.py
> index fba72629..d74c5db1 100644
> --- a/docs/conf.py
> +++ b/docs/conf.py
> @@ -71,7 +71,7 @@ master_doc = 'index'
>
> # General information about the project.
> project = 'Proxmox Backup'
> -copyright = '2019-2023, Proxmox Server Solutions GmbH'
> +copyright = '2019-2024, Proxmox Server Solutions GmbH'
> author = 'Proxmox Support Team'
>
> # The version info for the project you're documenting acts as a replacement for
i wonder whether it's worth following curl's example on this and just
get rid of the years [1]. seems needlessly tedious to maintain…
[1]: https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-10-02 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 15:58 Christoph Heiss
2024-10-02 9:22 ` Shannon Sterz [this message]
2024-10-02 9:42 ` Dietmar Maurer
2024-10-02 9:55 ` Shannon Sterz
2024-10-02 10:27 ` Dietmar Maurer
2024-11-27 11:43 ` [pbs-devel] applied: " Thomas Lamprecht
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=D4L7L9VPFO42.1NNKLUQRKV45C@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pbs-devel@lists.proxmox.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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal