From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 1/2] doc: use layered documentation instead of overwriting doc/guru.rsto
Date: Tue, 20 Jun 2023 15:03:14 +0200 [thread overview]
Message-ID: <ZJGjksNPbf13uc+M@pengutronix.de> (raw)
In-Reply-To: <20230510133915.1724757-1-rhi@pengutronix.de>
On Wed, May 10, 2023 at 03:39:15PM +0200, Roland Hieber wrote:
> Since PTXdist 2023.01.0, all files named index-layer-*.rst are included
> in the main toctree by upstream PTXdist, so there is no need anymore to
> fork the upstream guru.rst. See the docs for more info.
>
> We have to remove the :numbered: argument because the main toctree in
> the upstream guru.rst is already numbered, otherwise this will generate
> a warning.
>
> Link: https://www.ptxdist.org/doc/daily_work_section.html#integrate-project-specific-documentation-into-the-manual
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> doc/guru.rst | 17 -----------------
> doc/{index.rst => index-layer-1-distrokit.rst} | 2 --
> 2 files changed, 19 deletions(-)
> delete mode 100644 doc/guru.rst
> rename doc/{index.rst => index-layer-1-distrokit.rst} (87%)
Applied to next.
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
prev parent reply other threads:[~2023-06-20 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 13:39 Roland Hieber
2023-05-10 13:39 ` [DistroKit] [PATCH 2/2] doc: intro: link to license and Git history Roland Hieber
2023-06-20 13:03 ` Robert Schwebel
2023-06-20 13:03 ` Robert Schwebel [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=ZJGjksNPbf13uc+M@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=rhi@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