linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Flavio Suligoi <f.suligoi@asem.it>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] docs: acpi: fix old http link and improve document format
Date: Fri, 15 May 2020 11:40:54 -0600	[thread overview]
Message-ID: <20200515114054.2496c171@lwn.net> (raw)
In-Reply-To: <1588673836-9954-2-git-send-email-f.suligoi@asem.it>

On Tue, 5 May 2020 12:17:16 +0200
Flavio Suligoi <f.suligoi@asem.it> wrote:

> The website:
> 
>     http://wiki.minnowboard.org
> 
> doesn't exist anymore. The same pages are moved to:
> 
>     https://www.elinux.org/Minnowboard
> 
> Other improvements concern the introduction of some rst
> semantic markup in the document.
> 
> Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>

Thanks for updating the URL.  The markup changes are a bit heavy-handed,
though; could I ask you to redo it without that.  In particular, there is
no real need to put file paths in ``literal text``, but that does clutter
up the reading experience significantly.

Thanks,

jon

  reply	other threads:[~2020-05-15 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 10:17 [PATCH 1/2] docs: filesystems: add info about efivars content Flavio Suligoi
2020-05-05 10:17 ` [PATCH 2/2] docs: acpi: fix old http link and improve document format Flavio Suligoi
2020-05-15 17:40   ` Jonathan Corbet [this message]
2020-05-19  8:41     ` [PATCH v1 1/2] docs: filesystems: add info about efivars content Flavio Suligoi
2020-05-19  8:41       ` [PATCH v1 2/2] docs: acpi: fix old http link and improve document format Flavio Suligoi
2020-05-25 16:45       ` [PATCH v1 1/2] docs: filesystems: add info about efivars content Jonathan Corbet

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=20200515114054.2496c171@lwn.net \
    --to=corbet@lwn.net \
    --cc=f.suligoi@asem.it \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    /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).