From: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
To: Gyorgy Sarvari <skandigraun@gmail.com>,
openembedded-devel@lists.openembedded.org, akuster808@gmail.com
Cc: raj.khem@gmail.com, schnitzeltony@gmail.com
Subject: Re: [oe] [meta-multimedia] pipewire: Install missing ALSA config files
Date: Thu, 24 Apr 2025 09:58:08 -0300 [thread overview]
Message-ID: <c3828ecc-f52f-4eaa-93b1-45bac83f47dd@collabora.com> (raw)
In-Reply-To: <24d1fec7-7c32-494d-ba9f-cbe0ea6eca70@gmail.com>
Hi Gyorgy,
On 4/22/25 5:35 AM, Gyorgy Sarvari wrote:
>
> On 4/21/25 16:21, Ariel D'Alessandro via lists.openembedded.org wrote:
>> Armin,
>>
>> Could you take a look at this?
>
> I'm not Armin - but I think there is some misunderstanding about the
> backporting process.
>
> Backports are normally not requested, rather they are made when someone
> cares enough about the issue to make it happen: if you'd like a change
> from master to be present in a stable release, then you need to prepare
> the backported patch, and send it to this list.
Makes sense, sorry it's the first patch I send to this list and clearly
misunderstood these guidelines.
I've just sent a proper patch
https://lists.openembedded.org/g/openembedded-devel/message/117093
Thanks a lot for taking the time to explain.
Regards,
--
Ariel D'Alessandro
Software Engineer
Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718
prev parent reply other threads:[~2025-04-24 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1831E745EF300249.1841@lists.openembedded.org>
2025-04-21 14:21 ` [oe] [meta-multimedia] pipewire: Install missing ALSA config files Ariel D'Alessandro
2025-04-22 8:35 ` Gyorgy Sarvari
2025-04-24 12:58 ` Ariel D'Alessandro [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=c3828ecc-f52f-4eaa-93b1-45bac83f47dd@collabora.com \
--to=ariel.dalessandro@collabora.com \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=schnitzeltony@gmail.com \
--cc=skandigraun@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 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.