All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <lukakrstic031@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] patchtest: reject Upstream-Status after scissors
Date: Wed, 17 Dec 2025 08:13:46 +0100	[thread overview]
Message-ID: <DF0B0V3GOP92.D0RPEBV393KB@bootlin.com> (raw)
In-Reply-To: <20251215204507.1675-1-lukakrstic031@gmail.com>

On Mon Dec 15, 2025 at 9:45 PM CET, Luka Krstic via lists.openembedded.org wrote:
> From: l-krstic <lukakrstic031@gmail.com>
>
> Upstream-Status must be placed in the patch header before the
> scissors line. patchtest currently accepts tags that appear
> only after the scissors, which means the tag is lost when the
> patch is refreshed by git or devtool.
>
> Update test_upstream_status_presence_format() to distinguish
> between tags in the header and tags after the scissors, and
> reject the latter.
>
> Fixes: [YOCTO #15940]
> Signed-off-by: Luka Krstic <lukakrstic031@gmail.com>
> ---

Hi Luka,

Thanks for your patch.

It is conflicting a lot with existing code on master branch: are you
based on a recent master branch on your side?

Thanks,
Mathieu

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



  reply	other threads:[~2025-12-17  7:14 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 ` Mathieu Dubois-Briand [this message]
     [not found]   ` <CABTLy3aZichqpsbZn3m84i-6b7_FdDgoCSkig3=SYQYWLvA66Q@mail.gmail.com>
2025-12-17 12:20     ` [OE-core] " Mathieu Dubois-Briand
     [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=DF0B0V3GOP92.D0RPEBV393KB@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=lukakrstic031@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.