From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
"Laurent Vivier" <Laurent@vivier.eu>,
"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 13:33:24 +0000 [thread overview]
Message-ID: <YZucJGIZFKM7v3xa@redhat.com> (raw)
In-Reply-To: <ef4ff222-1053-904a-77c2-39adc9dd929a@redhat.com>
On Mon, Nov 22, 2021 at 02:30:10PM +0100, Thomas Huth 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?
Well if you run 'codespell' with no args on qemu.git right now, you
get over 5000 possible mistakes reported. Many (perhaps even most)
will be false positives, but with that amount of existing report,
I don't think its credible to request contributors to run this
and wade through its results to see if they made things worse or
not.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-11-22 13:37 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é [this message]
2021-11-22 13:38 ` Thomas Huth
2021-11-22 13:53 ` Peter Maydell
2021-11-22 14:01 ` Thomas Huth
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=YZucJGIZFKM7v3xa@redhat.com \
--to=berrange@redhat.com \
--cc=Laurent@vivier.eu \
--cc=alex.bennee@linaro.org \
--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 \
--cc=thuth@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).