public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] doc: documentation: Fix typo other => older
Date: Wed, 17 Apr 2024 14:19:10 +0200	[thread overview]
Message-ID: <20240417121910.GA727397@pevik> (raw)
In-Reply-To: <Zh-lvOimOYLd2Z4H@yuki>

> Hi!
> > I suppose you mean "older", otherwise the sentence does not make sense
> > to me (i.e. which versions caused problems?)

> Can we fix this one in the same patch as well?

> diff --git a/doc/developers/documentation.rst b/doc/developers/documentation.rst
> index 30dacd384..b56d5b4c7 100644
> --- a/doc/developers/documentation.rst
> +++ b/doc/developers/documentation.rst
> @@ -11,7 +11,7 @@ and it's built on top of `Sphinx <https://www.sphinx-doc.org/en/master/>`_.
>  Building documentation
>  ~~~~~~~~~~~~~~~~~~~~~~

> -First of all, to build the documentation we must be sure that all dependences
> +First of all, to build the documentation we must be sure that all dependencies

Sure, just waiting on Andrea's ack.

BTW how does these spellchecker feature in sphinx works? Did you find it to run something
(tox -e spelling -r [1] or did you spot it manually?

I hoped that errors like this would be caught, e.g. we might want to have CI
check for it, right?

Kind regards,
Petr

[1] https://sphinxcontrib-spelling.readthedocs.io/en/latest/run.html

>  have been installed (please check ``doc/requirements.txt`` file). Sometimes the
>  Linux distros are providing them, but the best way is to use ``virtualenv``

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-04-17 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 10:12 [LTP] [PATCH 1/1] doc: documentation: Fix typo other => older Petr Vorel
2024-04-17 10:34 ` Cyril Hrubis
2024-04-17 12:19   ` Petr Vorel [this message]
2024-04-17 12:22     ` Andrea Cervesato via ltp
2024-04-17 13:37     ` Cyril Hrubis
2024-04-17 18:32       ` Petr Vorel

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=20240417121910.GA727397@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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