From: Elijah Newren <newren@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Han-Wen Nienhuys" <hanwen@google.com>,
"Jeff King" <peff@peff.net>, "Taylor Blau" <me@ttaylorr.com>,
"René Scharfe" <l.s.r@web.de>
Subject: Re: What's cooking in git.git (Mar 2021, #03; Wed, 10)
Date: Thu, 11 Mar 2021 08:17:20 -0800 [thread overview]
Message-ID: <CABPp-BHLNm14c9Sxv6zWBod7wxK6gSWwt=SR3J4NVObAprcomQ@mail.gmail.com> (raw)
In-Reply-To: <87r1klhq3y.fsf@evledraar.gmail.com>
On Thu, Mar 11, 2021 at 3:44 AM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
>
> On Thu, Mar 11 2021, Junio C Hamano wrote:
>
> > Will merge to 'next'.
> > In the longer term, we might want to remove filter-branch and nudge
> > folks to more modern tools.
>
> Did we ever have a re-discussion of adding Elijah's
> git-filter-replacement-whose-name-I-always-forget to git.git? :)
git-filter-repo (https://github.com/newren/git-filter-repo)
The original discussion you were probably thinking of was at
https://lore.kernel.org/git/CABPp-BHqdKvsUDx40Tz-A3z32TN_KWcDENWb8zsaidxxf8SNCg@mail.gmail.com/.
Re-discussion was at
https://lore.kernel.org/git/CABPp-BEr8LVM+yWTbi76hAq7Moe1hyp2xqxXfgVV4_teh_9skA@mail.gmail.com/.
Resulted in https://lore.kernel.org/git/20190828002210.8862-1-newren@gmail.com/
instead.
next prev parent reply other threads:[~2021-03-11 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 3:01 What's cooking in git.git (Mar 2021, #03; Wed, 10) Junio C Hamano
2021-03-11 4:49 ` Elijah Newren
2021-03-11 6:08 ` Junio C Hamano
2021-03-11 5:20 ` ZheNing Hu
2021-03-11 5:28 ` Junio C Hamano
2021-03-11 6:18 ` ZheNing Hu
2021-03-11 11:44 ` Ævar Arnfjörð Bjarmason
2021-03-11 13:01 ` Han-Wen Nienhuys
2021-03-11 18:12 ` Junio C Hamano
2021-03-11 16:17 ` Elijah Newren [this message]
2021-03-11 18:27 ` Junio C Hamano
2021-03-11 19:17 ` Jeff King
2021-03-12 7:10 ` Junio C Hamano
2021-03-11 19:13 ` René Scharfe.
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='CABPp-BHLNm14c9Sxv6zWBod7wxK6gSWwt=SR3J4NVObAprcomQ@mail.gmail.com' \
--to=newren@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanwen@google.com \
--cc=l.s.r@web.de \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).