mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] Documentation/conf.py: fix copyright years
Date: Fri, 16 Sep 2022 14:41:00 +0300	[thread overview]
Message-ID: <20220916144100.fcd08e98d9ffc77a7d4d016e@gmail.com> (raw)
In-Reply-To: <20220916062843.GX6477@pengutronix.de>

On Fri, 16 Sep 2022 08:28:43 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:

Hi Sascha!

> On Thu, Sep 15, 2022 at 09:18:20AM +0300, Antony Pavlov wrote:
> > 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?
> 
> We have the theme here internally. Sorry, I can't give you any
> instructions on how to reproduce the docs as found on the website.
> What do you need them for?

I want to extend my gitlab.com CI-CD scripts.

-- 
Best regards,
  Antony Pavlov



  reply	other threads:[~2022-09-16 11:39 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
2022-09-16  6:28   ` Sascha Hauer
2022-09-16 11:41     ` Antony Pavlov [this message]
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=20220916144100.fcd08e98d9ffc77a7d4d016e@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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