From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4 feature request: run command before rewriting history
Date: Fri, 6 Mar 2026 16:14:28 -0500 [thread overview]
Message-ID: <20260306-mighty-raspberry-zebra-f3ab4b@lemur> (raw)
In-Reply-To: <87bjv7p435.fsf@toke.dk>
On Wed, Feb 12, 2025 at 04:36:46PM +0100, Toke Høiland-Jørgensen wrote:
> Toke Høiland-Jørgensen <toke@redhat.com> writes:
>
> > Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> >
> >> On Wed, Oct 30, 2024 at 11:16:15AM +0100, Toke Høiland-Jørgensen wrote:
> >>> > Do you think this would be feasible to implement?
> >>>
> >>> Hi Konstantin
> >>>
> >>> Friendly ping on the above? :)
> >>
> >> Yeah, I hope to be able to look into this in the near future. Unfortunately,
> >> I've been dealing with less-than-pleasant tasks such as ddos attacks and
> >> trolls over the past couple of weeks, but at least it's finally on the wane as
> >> people move on.
> >
> > Right, no worries, just wanted to make sure this didn't get lost
> > entirely. Thanks for looking at it! :)
>
> Hi Konstantin
>
> Another friendly ping on this? :)
Only a year later, finally adding this to the tracker. I'm sure you've given
up, but this has been sitting in my inbox for a while, shaming me.
bugspray tag b4/prep
--
KR
next prev parent reply other threads:[~2026-03-06 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 11:22 b4 feature request: run command before rewriting history Toke Høiland-Jørgensen
2024-10-30 10:16 ` Toke Høiland-Jørgensen
2024-10-30 17:36 ` Konstantin Ryabitsev
2024-10-31 10:29 ` Toke Høiland-Jørgensen
2025-02-12 15:36 ` Toke Høiland-Jørgensen
2026-03-06 21:14 ` Konstantin Ryabitsev [this message]
2026-03-06 21:18 ` B4 Bugbot
2026-03-19 21:38 ` B4 Bugbot
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=20260306-mighty-raspberry-zebra-f3ab4b@lemur \
--to=konstantin@linuxfoundation.org \
--cc=toke@redhat.com \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.org \
/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