From: "Guðni Már Gilbert" <gudnimar@noxmedical.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python3-bcrypt: drop python3-six from RDEPENDS
Date: Thu, 09 May 2024 16:30:14 -0700 [thread overview]
Message-ID: <32021.1715297414090759990@lists.openembedded.org> (raw)
In-Reply-To: <b8a927c998c3f362547676d1088625f0dfb4e66a.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
On Thu, May 9, 2024 at 04:49 PM, Richard Purdie wrote:
>
> Unfortunately these patches are coming through with corrupted
> whitespace which means they don't apply.
Hi Richard, thank you for letting me know, I had no idea about this!
I'm still pretty new in this mailing list so I hope I haven't been unknowingly posting corrupted patches the last month.
I'll check for this next time. (I'm using Ubuntu 22.04 for this work)
Best regards,
Gudni
[-- Attachment #2: Type: text/html, Size: 509 bytes --]
prev parent reply other threads:[~2024-05-09 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 12:01 [PATCH] python3-bcrypt: drop python3-six from RDEPENDS Guðni Már Gilbert
2024-05-09 16:49 ` [OE-core] " Richard Purdie
2024-05-09 23:30 ` Guðni Már Gilbert [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=32021.1715297414090759990@lists.openembedded.org \
--to=gudnimar@noxmedical.com \
--cc=openembedded-core@lists.openembedded.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).