From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][oe-core][PATCH] pam: update 1.6.1 -> 1.7.0
Date: Tue, 03 Dec 2024 14:59:51 +0100 [thread overview]
Message-ID: <R78XNS.UI8NYXWW9D1A2@t-online.de> (raw)
In-Reply-To: <180D59229FBE9F1F.18476@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Sent a v2 that adds the package split and more cleanup on top of the
upcoming libpam update and
On Mon, Dec 2 2024 at 12:37:08 +01:00:00, Markus Volk
<f_l_k@t-online.de> wrote:
> On Mon, Dec 2 2024 at 12:06:17 +01:00:00, Alexander Kanavin
> <alex.kanavin@gmail.com> wrote:
>> Please see my comment elsewhere, it's better to split this into
>> several patches, each dealing with a particular issue (in particular
>> the version update shouldn't be bundled with all the other changes).
>>
>> Alex
>
> Fair enough. I haven't gotten around to cleaning it up yet and there
> is also still
> a patch in it with ;apply=no that needs to be deleted. I'd better
> wait for the update
> and add the changes afterwards. I just wanted to submit the patch for
> review to see
> if that would even be an optionat all
[-- Attachment #2: Type: text/html, Size: 1119 bytes --]
prev parent reply other threads:[~2024-12-03 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 10:53 [RFC][oe-core][PATCH] pam: update 1.6.1 -> 1.7.0 Markus Volk
2024-12-02 11:06 ` Alexander Kanavin
2024-12-02 11:37 ` Markus Volk
[not found] ` <180D59229FBE9F1F.18476@lists.openembedded.org>
2024-12-03 13:59 ` Markus Volk [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=R78XNS.UI8NYXWW9D1A2@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.