Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Лука Крстић" <lukakrstic031@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"Steve Sakoman" <steve@sakoman.com>,
	"Yoann Congal" <yoann.congal@smile.fr>
Subject: Re: [OE-core] [PATCH] patchtest: reject Upstream-Status after scissors
Date: Wed, 17 Dec 2025 13:20:26 +0100	[thread overview]
Message-ID: <DF0HJNZXHLW4.2ZJNCZUGHYZ9F@bootlin.com> (raw)
In-Reply-To: <CABTLy3aZichqpsbZn3m84i-6b7_FdDgoCSkig3=SYQYWLvA66Q@mail.gmail.com>

On Wed Dec 17, 2025 at 8:25 AM CET, Лука Крстић wrote:
> Hi Mathieu,
>
> Thanks for the quick feedback.
> I am based on the scarthgap branch.
> I guess that is not good. Can you tell me what should be the base?
>

Hi Luka,

So I believe you wanted to get this patch merged in the scarthgap
branch, which raises two points:
- any change you want to contribute in a stable branch must have been
  first accepted in the master branch, except if it does not make sense
  to merge it in master.
- patches targeting a stable branch must include the branch name in the
  mail prefix.

More details can be found here:
https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html#submitting-changes-to-stable-release-branches

So given the content of your patch, I believe this should be first
merged in master.

Also, backport in stable branches should be reserved to bug or security
fixes. I'm not involved in this decision, but I'm not fully convinced
this patch meets the requirements.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2025-12-17 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 20:45 [PATCH] patchtest: reject Upstream-Status after scissors lukakrstic031
2025-12-17  7:13 ` [OE-core] " Mathieu Dubois-Briand
     [not found]   ` <CABTLy3aZichqpsbZn3m84i-6b7_FdDgoCSkig3=SYQYWLvA66Q@mail.gmail.com>
2025-12-17 12:20     ` Mathieu Dubois-Briand [this message]
     [not found]       ` <20251217204031.3022279-1-lukakrstic031@gmail.com>
2025-12-17 20:26         ` [PATCH v2] " Luka Krstic

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=DF0HJNZXHLW4.2ZJNCZUGHYZ9F@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=lukakrstic031@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.com \
    --cc=yoann.congal@smile.fr \
    /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