All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
Date: Wed, 26 Aug 2026 15:34:06 +0100	[thread overview]
Message-ID: <f7a6195f5b8b379f87370dc31b7a1fcbd5c95690.camel@linuxfoundation.org> (raw)
In-Reply-To: <1880129.1787221871218113438@lists.openembedded.org>

Hi Jaipaul,

On Thu, 2026-08-20 at 03:31 -0700, Jaipaul Cheernam via lists.openembedded.org wrote:
> Both oe-core and metaopenembedded serires are accepted. 
> 
> https://patchwork.yoctoproject.org/project/oe-core/list/?series=49858&archive=both&state=*
> https://patchwork.yoctoproject.org/project/oe/list/?series=49954&archive=both&state=*
>  
> Can you check on bitbake patch. 

I've given this one a lot of thought and also asked around the
community. The general consensus is we don't want to make the parser
this pedantic. I think it is fine to fix the whitespace issues and we
have done, but the extra complexity in the parser doesn't seem to be in
line with where people want to focus their time/energy right now. I'm
therefore probably not going to take the bitbake change.

Cheers,

Richard


      parent reply	other threads:[~2026-08-26 14:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  9:08 [PATCH] parse: warn on trailing whitespace after line continuation backslash Jaipaul Cheernam
2026-08-04 10:27 ` [bitbake-devel] " Richard Purdie
2026-08-04 10:37   ` Jaipaul Cheernam
2026-08-04 11:37     ` Richard Purdie
2026-08-04 12:15       ` Jaipaul Cheernam
2026-08-06 10:44 ` [PATCH v2] parse: warn on trailing whitespace in parsed lines Jaipaul Cheernam
2026-08-06 11:24 ` Jaipaul Cheernam
2026-08-13 15:07   ` [bitbake-devel] " Mathieu Dubois-Briand
2026-08-13 16:54     ` Jaipaul Cheernam
2026-08-20 10:31       ` Jaipaul Cheernam
2026-08-23  8:14         ` [bitbake-devel] " Mathieu Dubois-Briand
2026-08-25 16:13           ` Jaipaul Cheernam
2026-08-26 14:34         ` Richard Purdie [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=f7a6195f5b8b379f87370dc31b7a1fcbd5c95690.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=jaipaul.cheernam@est.tech \
    /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.