From: Igor Torrente <igormtorrente@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
corbet@lwn.net, gregkh@linuxfoundation.org,
grandmaster@al2klimov.de, rdunlap@infradead.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: Convert the Speakup guide to rst
Date: Tue, 1 Jun 2021 20:43:18 -0300 [thread overview]
Message-ID: <9932ed69-685a-e5ce-0180-bf030ca4b608@gmail.com> (raw)
In-Reply-To: <20210601215723.7kwakixrrizba3bu@begin>
Hi Samuel,
On 6/1/21 6:57 PM, Samuel Thibault wrote:
> Igor Torrente, le mar. 01 juin 2021 12:11:26 -0300, a ecrit:
>>>> +| acntsa -- Accent SA
>>>> +| acntpc -- Accent PC
>>>> +| apollo -- Apollo
>>>> +| audptr -- Audapter
>>>> +| bns -- Braille 'n Speak
>>>> +| dectlk -- DecTalk Express (old and new, db9 serial only)
>>>> +| decext -- DecTalk (old) External
>>>> +| dtlk -- DoubleTalk PC
>>>> +| keypc -- Keynote Gold PC
>>>> +| ltlk -- DoubleTalk LT, LiteTalk, or external Tripletalk (db9 serial only)
>>>> +| spkout -- Speak Out
>>>> +| txprt -- Transport
>>>> +| dummy -- Plain text terminal
>>>
>>> Looks like a definition list?
>>>
>>> https://docutils.sourceforge.io/docs/user/rst/quickref.html#definition-lists
>>
>> If the '|' is replaced by definition-list, I'll have to skip a line to each
>> item so the sphinx doesn't concatenate them into a single line. Like this:
>>
>> keywords
>> acntsa -- Accent SA
>>
>> acntpc -- Accent PC
>>
>> apollo -- Apollo
>> [...]
>>
>>
>> There's a way to do that without these blank lines?
>
> The blank line isn't really a problem.
>
>>>> +Document License
>>>> +================
>>>> +
>>>
>>> Using SPDX might be nice.
>>
>> I was just trying to respect the original text as much as possible, but I
>> don't mind change it if everybody agrees with it.
>
> SPDX should be fine.
I have two questions about it.
1 - Should I only make this change when we have the 'acks' from all the
previous contributors? Or can I change it to the v3?
2 - Is '.. SPDX-License-Identifier: GPL-2.0' at the beginning is enough?
>
> Samuel
>
Thanks,
---
Igor M. A. Torrente
next prev parent reply other threads:[~2021-06-01 23:43 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
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 [this message]
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=9932ed69-685a-e5ce-0180-bf030ca4b608@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 \
/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).