Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: dowan gullient <dowan.gullient@smile.fr>
Cc: chakrabortyshubham66@gmail.com, buildroot@buildroot.org,
	 Joseph Kogut <joseph.kogut@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/bash: bump to version 5.3
Date: Sat, 10 Oct 2026 19:49:01 +0200	[thread overview]
Message-ID: <asp5ttIPoT_UiyNg@windsurf> (raw)
In-Reply-To: <f3d370e6-5cb6-4f54-99ac-883afa561379@smile.fr>

Hello,

[Adding Joseph in Cc.]

On Fri, Jun 26, 2026 at 04:11:37PM +0200, dowan gullient via buildroot wrote:

> > +Upstream: N/A
> I think that marking these patches as "Upstream: N/A" might not be the best.
> Since these patches fix legitimate build failures in the Bash source code,
> they are relevant to the upstream maintainers. It might be better to also
> submit them to the bug-bash mailing list and provide a link to the archive,
> similar to what was done for patch 0002.

Clearly, patches against bash must be submitted upstream. We cannot
accept those patches with "Upstream: N/A".

Also, not sure why we need all those patches, if Yocto has a lot less:
https://layers.openembedded.org/layerindex/recipe/81/.

Could you rework this?

Also, Joseph was working on this version bump. Any progress, or
perhaps coordination effort?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-10 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 12:15 [Buildroot] [PATCH] package/bash: bump to version 5.3 Shubham Chakraborty
2026-06-26 14:11 ` dowan gullient via buildroot
2026-10-10 17:49   ` Thomas Petazzoni via buildroot [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=asp5ttIPoT_UiyNg@windsurf \
    --to=buildroot@buildroot.org \
    --cc=chakrabortyshubham66@gmail.com \
    --cc=dowan.gullient@smile.fr \
    --cc=joseph.kogut@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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