From: Nicolas Schier <nsc@kernel.org>
To: Askar Safin <safinaskar@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org
Subject: Re: [PATCH 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/
Date: Tue, 10 Mar 2026 07:24:34 +0100 [thread overview]
Message-ID: <aa-5IhUnf4CBKOuN@derry.ads.avm.de> (raw)
In-Reply-To: <20260310014912.3023668-1-safinaskar@gmail.com>
On Tue, Mar 10, 2026 at 04:49:12AM +0300, Askar Safin wrote:
> Nicolas Schier <nsc@kernel.org>:
> > +# Keep around until cleanup in scripts/remove-stale-files
>
> Linus said here https://lore.kernel.org/all/CAHk-=wiHK5_oBUdUiNAaevmN9f-ORe+QBqbRefAZaw-RbgEn3w@mail.gmail.com/
> that he doesn't like scripts/remove-stale-files (this is my interpretation).
thanks for the pointer!
Yes, remove-stale-files is suboptimal, but not adding entries there
doesn't make anything better. And yes, entries in remove-stale-files
should have a life-time of years rather than months; and removing
entries from .gitignore before the remove-stale-files cleanup should be
prevented.
Therefore I chose to add the comment to usr/.gitignore to prevent
accidental removal of the '/gen_init_cpio' before the time has come.
Does that match for you?
Kind regards,
Nicolas
next prev parent reply other threads:[~2026-03-10 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 7:56 [PATCH 0/2] Move tool for generating initramfs cpio to scripts/ Nicolas Schier
2026-03-09 7:56 ` [PATCH 1/2] kbuild: Mark usr_gen_init_cpio as no-dot-config-target Nicolas Schier
2026-03-09 7:56 ` [PATCH 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/ Nicolas Schier
2026-03-09 13:41 ` Thomas Weißschuh
2026-03-10 7:14 ` Nicolas Schier
2026-03-10 9:13 ` Thomas Weißschuh
2026-03-12 13:59 ` Nicolas Schier
2026-03-10 1:49 ` Askar Safin
2026-03-10 6:24 ` Nicolas Schier [this message]
2026-03-22 12:50 ` Askar Safin
2026-03-10 1:54 ` [PATCH 0/2] Move tool for generating initramfs cpio " Askar Safin
2026-03-10 4:30 ` H. Peter Anvin
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=aa-5IhUnf4CBKOuN@derry.ads.avm.de \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=safinaskar@gmail.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.