From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rpjday@crashcourse.ca,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] why i will be doing a bunch of proofreading for a while
Date: Fri, 05 Jun 2026 17:47:09 +0100 [thread overview]
Message-ID: <811dc0ab9bf8792c80d4eea04cf79dbf374841be.camel@linuxfoundation.org> (raw)
In-Reply-To: <7ad14a95-f630-5dc9-2920-03a347d0f3eb@crashcourse.ca>
On Fri, 2026-06-05 at 09:41 -0700, Robert P. J. Day via
lists.yoctoproject.org wrote:
> as of today, i am now between gigs so, while i look for another one
> in the area, i might as well pore over the docs and be annoyingly
> pedantic.
Perhaps rather than setting out to annoy us, try and focus that energy
onto something more productive? There are other ways to improve the
docs than just being pedantic...
Cheers,
Richard
prev parent reply other threads:[~2026-06-05 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 16:41 why i will be doing a bunch of proofreading for a while Robert P. J. Day
2026-06-05 16:47 ` Richard Purdie [this message]
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=811dc0ab9bf8792c80d4eea04cf79dbf374841be.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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