From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Quentin Schulz <foss@0leil.net>,
docs@lists.yoctoproject.org
Subject: Re: [docs] [master] Pull request
Date: Mon, 03 May 2021 13:41:25 +0100 [thread overview]
Message-ID: <bb2ca4f452f5f9c0897fd5518910598351848a83.camel@linuxfoundation.org> (raw)
In-Reply-To: <6224b355-782a-9c98-b1dc-7484a19a1fa3@bootlin.com>
On Mon, 2021-05-03 at 14:40 +0200, Michael Opdenacker wrote:
> Hi Richard,
>
> On 4/30/21 11:42 PM, Richard Purdie wrote:
> > Definitely not. I was trying to get some basic text pulled together on a couple of
> > topics but keep getting distracted. I should probably put that somewhere else locally
> > and stop it leaking out. It was meant to be done and sent long before now...
>
>
> Oops, I should have paid attention to this too.
>
> May I remove it from master-next so that I can submit the pull request
> again? I could keep a backup somewhere too.
I've merged it with it removed. It should/can be dropped from there and I'll
alter my scripts so I don't push there. Its just a bit of confusion from when
I was handling the docs patches...
Cheers,
Richard
next prev parent reply other threads:[~2021-05-03 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 17:58 [master] Pull request 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 [this message]
2021-05-03 12:43 ` Michael Opdenacker
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 18:47 Michael Opdenacker
2024-02-24 3:35 ` [docs] " Bruce Ashfield
2024-02-24 16:01 ` Michael Opdenacker
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-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=bb2ca4f452f5f9c0897fd5518910598351848a83.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=foss@0leil.net \
--cc=michael.opdenacker@bootlin.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