From: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncurses: bump to version 6.6-20260425
Date: Sun, 31 May 2026 12:22:38 +0530 [thread overview]
Message-ID: <ahvO8oJniQoAzSPz@fedora> (raw)
In-Reply-To: <ahte4jnN6VBRtafn@windsurf>
On 2026-05-31 00:05, Thomas Petazzoni wrote:
> 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.
I got the reference to the page from the repo itself
- https://github.com/mirror/ncurses/blob/master/ANNOUNCE
"Full manual pages are provided for the library and tools.
The ncurses distribution is available at ncurses' homepage:
https://invisible-island.net/archives/ncurses/ or
https://invisible-mirror.net/archives/ncurses/
"
The changelog can also be found in:
- https://github.com/mirror/ncurses/blob/master/NEWS
>
> Also, you're updating from 20251231 to 20260425, there have been
> multiple releases, so surely the changelog is longer than that.
I paraphrased the changelog incorrectly and incompletely:
- The poll()/errno fix is from 20260411:
https://invisible-island.net/ncurses/NEWS.html#t20260411
- The _nc_write_object, _nc_trim_sgr0, and read_SGR fixes are from
20260418:
https://invisible-island.net/ncurses/NEWS.html#t20260418
- The _nc_mouse_parse fix and konsole-direct/mintty/linux-alt1049
are from 20260404:
https://invisible-island.net/ncurses/NEWS.html#t20260404
> 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.
>
I used AI assistance when drafting the commit message, which contributed
to the inaccurate summaries. I should have verified the generated text more
carefully against the upstream changelog before submitting.
I will send a v2 with a proper commit message covering all intermediate
snapshots, written from the upstream NEWS file.
Best Regards,
Shubham
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-31 6:52 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
2026-05-31 6:52 ` Shubham Chakraborty [this message]
[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=ahvO8oJniQoAzSPz@fedora \
--to=chakrabortyshubham66@gmail.com \
--cc=buildroot@buildroot.org \
--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 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.