All of lore.kernel.org
 help / color / mirror / Atom feed
From: "AmateurECE" <ethan.twardy@gmail.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5
Date: Tue, 03 Dec 2024 09:03:52 -0600	[thread overview]
Message-ID: <D625OBSZYCB3.CNBANSTUR7WI@gmail.com> (raw)
In-Reply-To: <CAMKF1sqq7iu2AiQxBX2eqQX0P_sO1of_5ioCp7u5nj2hodYxcA@mail.gmail.com>

On Fri Nov 29, 2024 at 5:28 PM CST, Khem Raj wrote:
> Thanks for the patch, it is not done on top of master it seems. Please
> rebase it on master and resend if patch is needed for master
> otherwise mark the release branch in subject prefix. This will help
> route it correctly.

Thanks for getting back to me, Khem! I will rebase onto master and
resend the patch shortly. Please forgive my question, I'm unfamiliar
with the OpenEmbedded development process: I'd like this change to be
applied to both master and the scarthgap branch, since I'm currently
basing my work on scarthgap. In that case, should I submit two patches,
one to be applied to master, and one to be applied to scarthgap (with
[scarthgap] in the subject line)?

Ethan


  reply	other threads:[~2024-12-03 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24 16:54 [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5 AmateurECE
2024-11-29 23:28 ` [oe] " Khem Raj
2024-12-03 15:03   ` AmateurECE [this message]
2024-12-03 16:16     ` Khem Raj

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=D625OBSZYCB3.CNBANSTUR7WI@gmail.com \
    --to=ethan.twardy@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@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.