Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncurses: bump to version 6.6-20260425
Date: Sun, 31 May 2026 00:05:50 +0200	[thread overview]
Message-ID: <ahte4jnN6VBRtafn@windsurf> (raw)
In-Reply-To: <20260502173806.2666814-1-chakrabortyshubham66@gmail.com>

On Sat, May 02, 2026 at 11:08:05PM +0530, Shubham Chakraborty wrote:
> - Fix poll() handling for closed input with proper errno
> - Security fixes: limit-checks in _nc_write_object, _nc_trim_sgr0,
>   read_SGR, and _nc_mouse_parse
> - Terminal updates: konsole-direct, mintty, linux-alt1049
> - Various bug fixes and improvements

Where did you get this text from? It is nowhere to be found in
https://invisible-island.net/ncurses/NEWS.html.

Also, you're updating from 20251231 to 20260425, there have been
multiple releases, so surely the changelog is longer than that.

If you're using AI to generate those patches and their commit logs,
stop immediately. We don't have the time to review AI slop.

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-05-30 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02 17:38 [Buildroot] [PATCH] package/ncurses: bump to version 6.6-20260425 Shubham Chakraborty
2026-05-30 22:05 ` Thomas Petazzoni via buildroot [this message]
2026-05-31  6:52   ` Shubham Chakraborty
     [not found] <20260502173505.GA12345@buildroot.org>
2026-05-31  5:39 ` Shubham Chakraborty

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=ahte4jnN6VBRtafn@windsurf \
    --to=buildroot@buildroot.org \
    --cc=chakrabortyshubham66@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