From: Thomas Monjalon <thomas@monjalon.net>
To: Paul Szczepanek <paul.szczepanek@arm.com>
Cc: dev@dpdk.org, Luca Vizzarro <luca.vizzarro@arm.com>
Subject: Re: [PATCH v2] docs: remove html dir from nested docs
Date: Wed, 27 Nov 2024 13:35:09 +0100 [thread overview]
Message-ID: <5081661.X9hSmTKtgW@thomas> (raw)
In-Reply-To: <20241127114136.1102663-1-paul.szczepanek@arm.com>
27/11/2024 12:41, Paul Szczepanek:
> + # don't append html dir if dst is already nested in one but first
> + # remove the part of the path outside the tree in case html dir exists there
> + rel_path = os.path.relpath(dst, os.path.dirname(__file__))
> + html_dst = dst if 'html' in rel_path else join(dst, 'html')
What happens if the build directory is a completely different path
of the source tree?
Is there a risk of having the build directory inside a tree having /html/?
prev parent reply other threads:[~2024-11-27 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 16:25 [PATCH] dts: remove html dir from dts doc path Paul Szczepanek
2024-11-27 0:02 ` Thomas Monjalon
2024-11-27 11:41 ` [PATCH v2] docs: remove html dir from nested docs Paul Szczepanek
2024-11-27 12:35 ` Thomas Monjalon [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=5081661.X9hSmTKtgW@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).