linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Torrente <igormtorrente@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	speakup@linux-speakup.org, corbet@lwn.net,
	gregkh@linuxfoundation.org, grandmaster@al2klimov.de,
	rdunlap@infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: docs: Convert the Speakup guide to rst
Date: Wed, 2 Jun 2021 10:38:01 -0300	[thread overview]
Message-ID: <2044b3a6-45e1-5fe9-cabb-88a2758cde24@gmail.com> (raw)
In-Reply-To: <87pmx4pi29.fsf@intel.com>

Hi Jani,

On 6/2/21 9:27 AM, Jani Nikula wrote:
> On Tue, 01 Jun 2021, Igor Torrente <igormtorrente@gmail.com> wrote:
>> Hi Samuel,
>>
>> On 6/1/21 6:55 PM, Samuel Thibault wrote:
>>> Hello,
>>>
>>> Igor Torrente, le mar. 01 juin 2021 12:39:01 -0300, a ecrit:
>>>> I was reading all the emails sent in this thread, but I'm not sure how I
>>>> should proceed. Do think should I continue to improve the patch with the
>>>> Jani Nikula suggestions? Or abandon it? Or keep both versions?
>>>
>>> It seems that people are fine with the switch to the .rst format, and
>>> it'll indeed allow much better distribution of its content, so please
>>> continue improving the patch with the suggestions from Jani, you have an
>>>
>>> Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
>>>
>>> and the review will probably come from Jani, who seems to actually know
>>> a bit about the rst syntax :)
>>
>> OK, I will keep improving it.
> 
> Heh, I just made suggestions on things that I thought could be done
> better, but please see for yourself how it renders and how it actually
> works with Braille displays. That should have priority over anything I
> suggest.

I understand and agree. But I don't have a braille display to test the 
change, so I will need the help of the community anyway.

And if anything gets worse I can revert the changes in the next patch 
version based on the feedback.

> 
> BR,
> Jani.
> 
> 

Thanks,
---
Igor M. A. Torrente

  reply	other threads:[~2021-06-02 13:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 21:57 [PATCH v2] docs: Convert the Speakup guide to rst Igor Matheus Andrade Torrente
2021-05-31 22:07 ` Samuel Thibault
2021-05-31 22:40   ` Chime Hart
2021-05-31 22:42   ` Didier Spaier
2021-05-31 22:44     ` Samuel Thibault
2021-05-31 22:54       ` Samuel Thibault
     [not found]     ` <648b7668-1aa8-dc1d-c92e-7dfc8d3270a7@slint.fr>
2021-05-31 23:03       ` Didier Spaier
2021-06-01  2:11     ` Chris Brannon
2021-05-31 23:15   ` Gregory Nowak
2021-05-31 23:19     ` Samuel Thibault
2021-05-31 23:29     ` Didier Spaier
2021-05-31 23:39       ` Samuel Thibault
2021-05-31 23:31   ` Alexander Epaneshnikov
2021-06-01  4:17   ` Tom Fowle
2021-06-01 15:39   ` Igor Torrente
2021-06-01 21:55     ` Samuel Thibault
2021-06-01 23:32       ` Igor Torrente
2021-06-02 12:27         ` Jani Nikula
2021-06-02 13:38           ` Igor Torrente [this message]
2021-06-01 11:28 ` [PATCH v2] " Jani Nikula
2021-06-01 15:11   ` Igor Torrente
2021-06-01 15:51     ` Jani Nikula
2021-06-01 21:58       ` Samuel Thibault
2021-06-01 21:57     ` Samuel Thibault
2021-06-01 23:43       ` Igor Torrente
2021-06-01 18:53 ` Jonathan Corbet
2021-06-01 22:06   ` Samuel Thibault
2021-06-01 22:18     ` Jonathan Corbet
2021-06-01 22:37       ` Samuel Thibault
2021-06-01 22:44         ` Samuel Thibault
2021-06-01 22:45           ` Samuel Thibault
2021-06-01 22:48             ` Samuel Thibault
2021-06-02  0:54               ` Kirk Reiser
2021-06-02  0:55                 ` Kirk Reiser
2021-06-01 22:47         ` Jonathan Corbet
2021-06-02  6:47           ` Samuel Thibault
2021-06-02  2:54         ` Chris Brannon
2021-06-02  6:46           ` Samuel Thibault
2021-06-04 13:21       ` Greg KH

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=2044b3a6-45e1-5fe9-cabb-88a2758cde24@gmail.com \
    --to=igormtorrente@gmail.com \
    --cc=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.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).