From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
YP docs mailing list <docs@lists.yoctoproject.org>,
Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: Re: [docs] [master] Pull request
Date: Sat, 24 Feb 2024 17:01:42 +0100 [thread overview]
Message-ID: <8c42d162-0787-49d0-b185-e152ddb38690@bootlin.com> (raw)
In-Reply-To: <CADkTA4Mpr_jgh7MUYFo1vMC6amMFdOTz3yA1Bh3CJz24KYgmYw@mail.gmail.com>
Hi Bruce,
On 2/24/24 at 04:35, Bruce Ashfield wrote:
> On Fri, Feb 23, 2024 at 1:47 PM Michael Opdenacker via
> lists.yoctoproject.org
> <michael.opdenacker=bootlin.com@lists.yoctoproject.org> wrote:
>> Hi Richard,
>>
>> The following changes since commit 79530aeb97976b9a63bf04ed247f98061fc9d737:
>>
>> release-notes-4.3: fix spacing (2024-02-05 15:22:33 +0100)
>>
>> are available in the Git repository at:
>>
>> git://git.yoctoproject.org/yocto-docs master-next
>>
>> for you to fetch changes up to b63e6a5ac71b347961037b7ee496c2e958ad22c5:
>>
>> dev-manual: packages: need enough free space (2024-02-23 09:50:37 +0100)
>>
>> ----------------------------------------------------------------
>> Adrian Freihofer (1):
>> sdk-manual: extensible.rst: cover devtool ide-sdk
>>
>> Khem Raj (1):
>> ref-manual: variables: remove PYTHON_PN
>>
>> Lee Chee Yang (1):
>> migration-guide: add release notes for 4.3.3
>>
>> Michael Opdenacker (5):
>> ref-manual: system-requirements: update packages to build docs
>> ref-manual: release-process: grammar fix
>> manuals: suppress excess use of "following" word
>> dev-manual: packages: clarify shared PR service constraint
>> dev-manual: packages: need enough free space
>>
>> Simone Weiß (1):
>> dev-manual: Rephrase spdx creation
>>
>> Vyacheslav Yurkov (1):
>> manuals: kernel-dev: Fix BSP in recipe space
> As I commented on the patch itself, the above documentation tweak
> isn't correct and should be dropped.
Oops, thanks for highlighting this.
I removed this commit from my branch.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-02-24 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 18:47 [master] Pull request Michael Opdenacker
2024-02-24 3:35 ` [docs] " Bruce Ashfield
2024-02-24 16:01 ` Michael Opdenacker [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 13:26 Michael Opdenacker
2023-10-20 13:42 ` Richard Purdie
2023-10-20 13:52 ` [docs] " Michael Opdenacker
[not found] <177C70532F319E37.30507@lists.yoctoproject.org>
2023-08-18 9:38 ` Michael Opdenacker
[not found] <17073A7A4D84FFDA.608@lists.yoctoproject.org>
[not found] ` <6d373d8d-6f24-8457-efb7-09c50c56958c@bootlin.com>
2022-08-12 22:12 ` Richard Purdie
[not found] <8d2564aa-adde-1ed9-b303-5572326d9733@bootlin.com>
2022-07-20 13:08 ` Quentin Schulz
2022-07-20 13:25 ` Richard Purdie
[not found] <288d00ca-e20d-fafa-5962-6086504141ad@bootlin.com>
[not found] ` <cfd4049897d8631c458d9ff916b1d956ab55a810.camel@linuxfoundation.org>
[not found] ` <16D4F2CEEB1A79AE.28672@lists.yoctoproject.org>
[not found] ` <54127154-cef1-101f-bcae-31dc6f380649@bootlin.com>
[not found] ` <046477f4c63a2c6f088e65f9cb3916c11d421d2b.camel@linuxfoundation.org>
2022-02-18 18:03 ` Michael Opdenacker
2022-02-18 18:05 ` Richard Purdie
[not found] <1698C6B54DCB3A17.29205@lists.yoctoproject.org>
2021-08-09 8:23 ` Michael Opdenacker
2021-04-30 17:58 Michael Opdenacker
2021-04-30 20:56 ` [docs] " Quentin Schulz
2021-04-30 21:42 ` Richard Purdie
2021-05-03 12:40 ` Michael Opdenacker
2021-05-03 12:41 ` Richard Purdie
2021-05-03 12:43 ` Michael Opdenacker
2021-04-23 15:33 Michael Opdenacker
2021-04-23 15:49 ` Richard Purdie
2021-04-23 16:40 ` [docs] " Michael Opdenacker
[not found] <1676103AA4A595B2.28347@lists.yoctoproject.org>
2021-04-16 18:07 ` Michael Opdenacker
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=8c42d162-0787-49d0-b185-e152ddb38690@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bruce.ashfield@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=uvv.mail@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