[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiQLG6n97zuW3p_N_jTDtG-xWJDNGDAgvmjtwd5GYET4A@mail.gmail.com>
Date: Sun, 1 Jun 2025 11:24:34 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Kees Cook <kees@...nel.org>, linux-kernel@...r.kernel.org,
Eric Biggers <ebiggers@...nel.org>, Ingo Saitz <ingo@...nover.ccc.de>,
kernel test robot <oliver.sang@...el.com>, Marco Elver <elver@...gle.com>,
Nathan Chancellor <nathan@...nel.org>, Thiago Jung Bauermann <thiago.bauermann@...aro.org>
Subject: Re: [GIT PULL] hardening fixes for v6.16-rc1
On Sun, 1 Jun 2025 at 10:49, Konstantin Ryabitsev
<konstantin@...uxfoundation.org> wrote:
>
> It's working as designed, I'm afraid -- git-filter-repo is a powerful tool
> for rewriting git history and will happily fire off even when you are pointing
> it at your own two feet.
Yeah, well, it's designed for rewriting the repo.
But it most certainly can also rewrite the committer name, email and date.
And I do think that even if you check that the committer doesn't
change, you *should* make it rewrite the commit date, so that people
see when the thing was used to rebase commits.
Afaik, that's as easy as just setting the 'committer_date' member in
the commit callback. No?
Linus
Powered by blists - more mailing lists