public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <adongare@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [Whinlatter] [PATCH V3] vim: Fix CVE-2026-26269
Date: Mon, 30 Mar 2026 22:54:40 +0200	[thread overview]
Message-ID: <DHGEZI37ZFEP.2OYU0NJUB8E9X@smile.fr> (raw)
In-Reply-To: <725242.1774895334350588732@lists.openembedded.org>

On Mon Mar 30, 2026 at 8:28 PM CEST, Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> Hi Yoann,
>
> Thanks again for the review. Similar to the previous patch, I have verified the code and confirmed that the format matches the upstream repository exactly.
>
> The context lines starting with tabs in this patch reflect the original indentation used in the upstream src/netbeans.c source file for that specific block. I kept the tabs identical to the upstream commit to prevent any whitespace mismatch or indentation errors when applying the patch.
>
> Please let me know if you would still prefer me to convert these to spaces!
>
> Thanks, Anil

I answered about the format there:
https://lists.openembedded.org/g/openembedded-core/message/234256
This is the same issue here.

Regards,
-- 
Yoann Congal
Smile ECS



      reply	other threads:[~2026-03-30 20:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  7:02 [OE-core] [Whinlatter] [PATCH 1/2] vim v9.1.1683: Fix CVE-2026-25749 Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-09  7:02 ` [OE-core] [Whinlatter] [PATCH 2/2] vim v9.1.1683: Fix CVE-2026-26269 Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-10 23:56 ` [OE-core] [Whinlatter] [PATCH 1/2] vim v9.1.1683: Fix CVE-2026-25749 Yoann Congal
2026-03-11  9:13   ` Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-11  9:45     ` [OE-core] [scarthgap] [PATCH V2 1/2] vim: " Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-11  9:45       ` [OE-core] [scarthgap] [PATCH V2 2/2] vim: Fix CVE-2026-26269 Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-19 23:52       ` [OE-core] [scarthgap] [PATCH V2 1/2] vim: Fix CVE-2026-25749 Yoann Congal
2026-03-30 18:21         ` Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-30 20:52           ` [OE-core] " Yoann Congal
2026-03-31  8:54             ` Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-31 11:18               ` [OE-core] " Yoann Congal
2026-03-11  9:51     ` [OE-core] [Whinlatter] " Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-11  9:51       ` [OE-core] [Whinlatter] [PATCH V2 2/2] vim: Fix CVE-2026-26269 Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-11 11:24         ` Yoann Congal
2026-03-16 12:35           ` Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-16 13:59             ` [OE-core] [Whinlatter] [PATCH V3] " Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-19 23:54               ` Yoann Congal
2026-03-30 18:28                 ` Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-30 20:54                   ` Yoann Congal [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=DHGEZI37ZFEP.2OYU0NJUB8E9X@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=adongare@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox