From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Sanjeev Gupta <ghane0@gmail.com>
Cc: linux-doc@vger.kernel.org, corbet@lwn.net,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 2/3] Documentation/translations/it_IT: switch some links to https
Date: Fri, 11 Jun 2021 15:52:20 +0200 [thread overview]
Message-ID: <588d1ea5bdea1a60702e8ef51d234b01@vaga.pv.it> (raw)
In-Reply-To: <d6364079.AVcAADGh3uAAAAAAAAAAAKAiBwkAAAAAAMcAAAAAAA6qeABgvu8L@mailjet.com>
On 2021-06-08 06:15, Sanjeev Gupta wrote:
> Links have been checked to ensure that the old and new URL
> return the same page. This is not true for many links.
>
> Signed-off-by: Sanjeev Gupta <ghane0@gmail.com>
> ---
> .../translations/it_IT/doc-guide/kernel-doc.rst | 2 +-
> Documentation/translations/it_IT/doc-guide/sphinx.rst | 10 +++++-----
> Documentation/translations/it_IT/process/changes.rst | 2 +-
> .../translations/it_IT/process/coding-style.rst | 2 +-
> 4 files changed, 8 insertions(+), 8 deletions(-)
Acked-by: Federico Vaga <federico.vaga@vaga.pv.it>
Of course, there is nothing wrong with the patch, so it can be applied.
But, I give you exactly the same comment I gave you last time (see
inline)
> diff --git a/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
> b/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
> index 009cdac014b6..4d22df6a59d6 100644
> --- a/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
> +++ b/Documentation/translations/it_IT/doc-guide/kernel-doc.rst
> @@ -24,7 +24,7 @@ vengono filtrare per cercare i riferimenti ed i
> marcatori.
>
> Vedere di seguito per maggiori dettagli.
>
> -.. _`dominio Sphinx per il C`:
> http://www.sphinx-doc.org/en/stable/domains.html
> +.. _`dominio Sphinx per il C`:
> https://www.sphinx-doc.org/en/stable/domains.html
>
> Tutte le funzioni esportate verso i moduli esterni utilizzando
> ``EXPORT_SYMBOL`` o ``EXPORT_SYMBOL_GPL`` dovrebbero avere un commento
> diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst
> b/Documentation/translations/it_IT/doc-guide/sphinx.rst
> index 0046d75d9a70..f7db5db3766f 100644
> --- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
> +++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
> @@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate
> comandi ``make htmldocs`` o
> ``make pdfdocs``. La documentazione così generata sarà disponibile
> nella
> cartella ``Documentation/output``.
>
> -.. _Sphinx: http://www.sphinx-doc.org/
> +.. _Sphinx: https://www.sphinx-doc.org/
> .. _reStructuredText: http://docutils.sourceforge.net/rst.html
Can you convert the reStructuredText link to https?
https://docutils.sourceforge.io/rst.html
> I file reStructuredText possono contenere delle direttive che
> permettono di
> @@ -175,7 +175,7 @@ Aggiungere nuova documentazione è semplice:
> 2. aggiungete un riferimento ad esso nell'indice (`TOC tree`_) in
> ``Documentation/index.rst``.
>
> -.. _TOC tree: http://www.sphinx-doc.org/en/stable/markup/toctree.html
> +.. _TOC tree: https://www.sphinx-doc.org/en/stable/markup/toctree.html
>
> Questo, di solito, è sufficiente per la documentazione più semplice
> (come
> quella che state leggendo ora), ma per una documentazione più
> elaborata è
> @@ -191,8 +191,8 @@ informazione circa le loro potenzialità. In
> particolare, il
> cui cominciare. Esistono, inoltre, anche alcuni
> `costruttori specifici per Sphinx`_.
>
> -.. _`manuale introduttivo a reStructuredText`:
> http://www.sphinx-doc.org/en/stable/rest.html
> -.. _`costruttori specifici per Sphinx`:
> http://www.sphinx-doc.org/en/stable/markup/index.html
> +.. _`manuale introduttivo a reStructuredText`:
> https://www.sphinx-doc.org/en/stable/rest.html
> +.. _`costruttori specifici per Sphinx`:
> https://www.sphinx-doc.org/en/stable/markup/index.html
>
> Guide linea per la documentazione del kernel
> --------------------------------------------
> @@ -417,7 +417,7 @@ formato SVG (:ref:`it_svg_image_example`)::
> Le direttive del kernel per figure ed immagini supportano il formato
> **DOT**,
> per maggiori informazioni
>
> -* DOT: http://graphviz.org/pdf/dotguide.pdf
> +* DOT: https://graphviz.org/pdf/dotguide.pdf
> * Graphviz: http://www.graphviz.org/content/dot-language
Can you convert also the Graphviz link to https?
https://graphviz.org/doc/info/lang.html
> Un piccolo esempio (:ref:`it_hello_dot_file`)::
> diff --git a/Documentation/translations/it_IT/process/changes.rst
> b/Documentation/translations/it_IT/process/changes.rst
> index 87d081889bfc..b5a326379d5d 100644
> --- a/Documentation/translations/it_IT/process/changes.rst
> +++ b/Documentation/translations/it_IT/process/changes.rst
> @@ -497,4 +497,4 @@ Documentazione del kernel
> Sphinx
> ------
>
> -- <http://www.sphinx-doc.org/>
> +- <https://www.sphinx-doc.org/>
> diff --git a/Documentation/translations/it_IT/process/coding-style.rst
> b/Documentation/translations/it_IT/process/coding-style.rst
> index 95f2e7c985e2..2a0e8bc0f688 100644
> --- a/Documentation/translations/it_IT/process/coding-style.rst
> +++ b/Documentation/translations/it_IT/process/coding-style.rst
> @@ -1166,7 +1166,7 @@ ISBN 0-201-61586-X.
>
> Manuali GNU - nei casi in cui sono compatibili con K&R e questo
> documento -
> per indent, cpp, gcc e i suoi dettagli interni, tutto disponibile qui
> -http://www.gnu.org/manual/
> +https://www.gnu.org/manual/
>
> WG14 è il gruppo internazionale di standardizzazione per il linguaggio
> C,
> URL: http://www.open-std.org/JTC1/SC22/WG14/
--
Federico Vaga
parent reply other threads:[~2021-06-11 13:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <d6364079.AVcAADGh3uAAAAAAAAAAAKAiBwkAAAAAAMcAAAAAAA6qeABgvu8L@mailjet.com>]
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=588d1ea5bdea1a60702e8ef51d234b01@vaga.pv.it \
--to=federico.vaga@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=ghane0@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=unixbhaskar@gmail.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).