qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Kashyap Chamarthy" <kchamart@redhat.com>,
	qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
	"Laurent Vivier" <Laurent@vivier.eu>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH 1/2] docs: Fix botched rST conversion of 'submitting-a-patch.rst'
Date: Mon, 22 Nov 2021 15:01:58 +0100	[thread overview]
Message-ID: <a2087e9c-82cb-8cc6-e580-9cc27891c196@redhat.com> (raw)
In-Reply-To: <CAFEAcA-+38PB3aOypgbAmeJN-X3P2gzB5K+CTAveXdt7jmF3mw@mail.gmail.com>

On 22/11/2021 14.53, Peter Maydell wrote:
> On Mon, 22 Nov 2021 at 13:30, Thomas Huth <thuth@redhat.com> wrote:
>>
>> On 22/11/2021 14.25, Peter Maydell wrote:
>>> On Mon, 22 Nov 2021 at 12:37, Thomas Huth <thuth@redhat.com> wrote:
>>>> What about simply replacing it with a new sentence below the bullet list,
>>>> saying:
>>>>
>>>> "Please also use a spell checker like `codespell
>>>> https://github.com/codespell-project/codespell` with your patches"
>>>
>>> How many regular contributors actually do that?
>>
>> Considering the typos that we have in the code, not enough ;-)
>>
>> Anyway, it's just a polite recommendation here, not a must-do, so mentioning
>> codespell here doesn't really hurt, does it?
> 
> I don't think we should be recommending to new contributors that
> they do things that established contributors generally do not do.
> The document has enough "things you should do or think about" already.
> My preference would be for simply not mentioning spelling-checking.
> 
> (If we do want to come up with some process for dealing with
> spelling issues in the codebase, then we either need to put it
> into CI so it's run automatically, or we need to have something
> that works on the individual patch level.)

Ok ... In any case - seems like this needs more discussion, so I'll drop it 
from the patch for now. We can still add some wording or CI magic later, but 
that's certainly something that we rather want to do after version 6.2 has 
been released...

  Thomas



  reply	other threads:[~2021-11-22 14:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 19:31 [PATCH 0/2] Fix broken rST conversion of "submitting-a-patch.rst" Kashyap Chamarthy
2021-11-19 19:31 ` [PATCH 1/2] docs: Fix botched rST conversion of 'submitting-a-patch.rst' Kashyap Chamarthy
2021-11-22  9:51   ` Thomas Huth
2021-11-22 10:20     ` Kashyap Chamarthy
2021-11-22 10:36       ` Thomas Huth
2021-11-22 12:19         ` Kashyap Chamarthy
2021-11-22 12:36           ` Thomas Huth
2021-11-22 12:59             ` Kashyap Chamarthy
2021-11-22 13:25             ` Peter Maydell
2021-11-22 13:30               ` Thomas Huth
2021-11-22 13:33                 ` Daniel P. Berrangé
2021-11-22 13:38                   ` Thomas Huth
2021-11-22 13:53                 ` Peter Maydell
2021-11-22 14:01                   ` Thomas Huth [this message]
2021-11-22 14:45                     ` Kashyap Chamarthy
2021-11-19 19:31 ` [PATCH 2/2] docs: List more commit-message tags "in submitting-a-patch" Kashyap Chamarthy
2021-11-19 20:19 ` [PATCH 0/2] Fix broken rST conversion of "submitting-a-patch.rst" Eric Blake

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=a2087e9c-82cb-8cc6-e580-9cc27891c196@redhat.com \
    --to=thuth@redhat.com \
    --cc=Laurent@vivier.eu \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).