From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/bash-completion: bump to version 2.17.0
Date: Sun, 31 May 2026 00:10:31 +0200 [thread overview]
Message-ID: <ahtflblRB-XoMzK1@windsurf> (raw)
In-Reply-To: <20260412182023.96383-1-chakrabortyshubham66@gmail.com>
On Sun, Apr 12, 2026 at 11:50:22PM +0530, Shubham Chakraborty wrote:
> - Enhanced smartctl completion support
> - Added recursive directory handling improvements
> - Fixed rsync/scp/ssh file type handling
> - Improved BSD compatibility for rsync
> - Fixed chgrp completion typo
Where does this invented changelog comes from? Seems like a vague
summary generated by AI. Stop using AI to generate Buildroot
patches. We will reject all your patches if you continue to spam us
with contributions generated by AI.
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 9e9c8a5a0f..9b123af415 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -3062,6 +3062,7 @@ F: package/wolfssl/
> N: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
> F: package/ccache/
> F: package/hyperfine/
> +F: package/bash-completion/
Alphabetic ordering is not correct.
> diff --git a/package/bash-completion/bash-completion.hash b/package/bash-completion/bash-completion.hash
> index 7e952e5b02..294ab65a2b 100644
> --- a/package/bash-completion/bash-completion.hash
> +++ b/package/bash-completion/bash-completion.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 73a8894bad94dee83ab468fa09f628daffd567e8bef1a24277f1e9a0daf911ac bash-completion-2.11.tar.xz
> -sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 COPYING
> +sha256 dd9d825e496435fb3beba3ae7bea9f77e821e894667d07431d1d4c8c570b9e58 bash-completion-2.17.0.tar.xz
> +sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643 COPYING
Changes to license files must be explained in the commit message.
But again: stop using AI. Focus on quality instead of quantity. You
are burning limited and precious maintainer review time.
Best regards,
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
next prev parent reply other threads:[~2026-05-30 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 18:20 [Buildroot] [PATCH] package/bash-completion: bump to version 2.17.0 Shubham Chakraborty
2026-05-30 22:10 ` Thomas Petazzoni via buildroot [this message]
2026-05-31 7:02 ` 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=ahtflblRB-XoMzK1@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