From: Antony Pavlov <antonynpavlov@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] Documentation/conf.py: fix copyright years
Date: Thu, 15 Sep 2022 09:18:20 +0300 [thread overview]
Message-ID: <20220915091820.aa57cf6dd4cabd1878e6d849@gmail.com> (raw)
In-Reply-To: <20220912084627.84575-1-antonynpavlov@gmail.com>
On Mon, 12 Sep 2022 11:46:27 +0300
Antony Pavlov <antonynpavlov@gmail.com> wrote:
Hi Sascha!
Here is the barebox documentation generated in my gitlab CI/CD system with 'make docs':
https://frantony.gitlab.io/-/barebox/-/jobs/3029093142/artifacts/Documentation/html/index.html
and this is the barebox documentation from barebox.org:
https://www.barebox.org/doc/latest/index.html
The index.html pages look different (different color scheme is used, no barebox logo in the left top
conner after 'make docs' etc).
Could you please publish an instruction how to reproduce barebox html documentation from barebox.org?
> N.B. N-dash is used!
>
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> ---
> Documentation/conf.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index bcd8633c919..5fb8b07c380 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -44,7 +44,7 @@ master_doc = 'index'
>
> # General information about the project.
> project = u'barebox'
> -copyright = u'2014, The barebox project'
> +copyright = u'2014–2022, The barebox project'
>
> # The version info for the project you're documenting, acts as replacement for
> # |version| and |release|, also used in various other places throughout the
> --
> 2.37.2
>
--
Best regards,
Antony Pavlov
next prev parent reply other threads:[~2022-09-15 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 8:46 Antony Pavlov
2022-09-15 6:18 ` Antony Pavlov [this message]
2022-09-16 6:28 ` Sascha Hauer
2022-09-16 11:41 ` Antony Pavlov
2022-09-16 6:29 ` Sascha Hauer
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=20220915091820.aa57cf6dd4cabd1878e6d849@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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