public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)" <adongare@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap] [PATCH V2 1/2] vim: Fix CVE-2026-25749
Date: Tue, 31 Mar 2026 01:54:47 -0700	[thread overview]
Message-ID: <173697.1774947287519751568@lists.openembedded.org> (raw)
In-Reply-To: <DHGEY5KEC0UG.1XDWZWAJC5ZTL@smile.fr>

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

Hi Yoann,

Thank you for the detailed explanation! That makes perfect sense now. I misunderstood and was looking at the source code indentation rather than the unified diff format itself. I clearly see now via cat -t that the context line indicator was a tab instead of a space.

I will regenerate the patch properly (I'll look into using devtool as you recommended) and send out an updated version.

Going forward, besides manually checking the diff, is there a specific script or tool (like a patch checker) you recommend using to verify the patch format is strictly correct before sending it to the mailing list?

Thanks again for your patience and help!

Best regards, Anil

[-- Attachment #2: Type: text/html, Size: 1003 bytes --]

  reply	other threads:[~2026-03-31  8: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) [this message]
2026-03-31 11:18               ` 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                   ` [OE-core] " Yoann Congal

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=173697.1774947287519751568@lists.openembedded.org \
    --to=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