From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
than.matos+bitbake@gmail.com,
bitbake-devel@lists.openembedded.org
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [bitbake-devel] Typo on the BitBake Documentation
Date: Wed, 4 Jan 2023 10:09:21 +0100 [thread overview]
Message-ID: <06079ed7-7f81-c869-e141-b62d29497585@bootlin.com> (raw)
In-Reply-To: <dee6ed9a3beabd5cd18042c61b0dfd31c2c4ff8e.camel@linuxfoundation.org>
Hi Richard,
Am 03.01.23 um 23:24 schrieb Richard Purdie:
> On Tue, 2022-12-27 at 13:00 -0800, than.matos+bitbake@gmail.com wrote:
>> I'm not sure if this is the right place to report and if I'm writing
>> in the wrong place, please feel free to remove this post.
>>
>> I'm also not a native of English, but I think there is a typo on the
>> BitBake documentation page.
>>
>>> You can obtain BitBake several different ways:
>> I feel like there is a missing `in` before the word `several`.
>>
>> Sorry to bother you!
> Thanks for reporting it.
>
> I'm a little torn on this. I am a native speaker and I'd have said it
> was probably sounds better as it is now. Adding "in" could likely be
> argued to me more grammatically correct and more formal for a written
> document but it doesn't feel quite right to me. I suspect it is one of
> those cases where there isn't a 100% correct answer.
Thanks for the native advice!
What about "There are several ways to obtain BitBake"?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-01-04 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bWm9.1672174859052782246.2l5k@lists.openembedded.org>
2023-01-03 15:03 ` [bitbake-devel] Typo on the BitBake Documentation Quentin Schulz
2023-01-03 17:04 ` [docs] " Peter Kjellerstedt
[not found] ` <dee6ed9a3beabd5cd18042c61b0dfd31c2c4ff8e.camel@linuxfoundation.org>
2023-01-04 9:09 ` Michael Opdenacker [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=06079ed7-7f81-c869-e141-b62d29497585@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=than.matos+bitbake@gmail.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