[ Sending this to #932957 as well, as it contains valueable info on that topic ]
Jeremy Stanley wrote (Wed, 24 May 2023 18:22:09 +):
> On 2023-05-24 19:40:56 +0200 (+0200), Agathe Porte wrote:
> [...]
> > Maybe the idea was to introduce %OLD_RELEASE_NAME% and to call sed to
> > replace this
On 2023-05-24 19:40:56 +0200 (+0200), Agathe Porte wrote:
[...]
> Maybe the idea was to introduce %OLD_RELEASE_NAME% and to call sed to
> replace this kind of strings in a build step, and not rely on sphinx
> substitution at all.
>
> I know that I have done this a few times and it works fine as a
Hi,
2023-05-20 23:36 CEST, Holger Wansing:
> Hi,
>
> RL wrote (Sat, 20 May 2023 12:52:25
> +0100):
> > Holger Wansing writes:
> >
> > > However, I may have some objections against the migration at all:
> > > as far as I know, sphinx/reStructuredText is still lacking some
> > > functionality,
>
Hi,
RL wrote (Sat, 20 May 2023 12:52:25
+0100):
> Holger Wansing writes:
>
> > However, I may have some objections against the migration at all:
> > as far as I know, sphinx/reStructuredText is still lacking some
> > functionality,
> > which is heavily used in the release-notes.
> > That is t
Holger Wansing writes:
> However, I may have some objections against the migration at all:
> as far as I know, sphinx/reStructuredText is still lacking some functionality,
> which is heavily used in the release-notes.
> That is the use of substitutions within URLs.
> In docbook speach these were
[[ debian-devel in CC, to get a wider audience regarding reStructuredText ]]
Hi,
I worked on this recently, and I have something like a prototype ready.
It can be found (as html) at
https://people.debian.org/~holgerw/release-notes_sphinx/
while the git repo containing the migration is at
https:/
6 matches
Mail list logo
