From: Elijah Newren <newren@gmail.com>
To: Git Mailing List <git@vger.kernel.org>, git-packagers@googlegroups.com
Subject: [ANNOUNCE] git-filter-repo 2.45.0
Date: Thu, 18 Jul 2024 19:56:19 -0700 [thread overview]
Message-ID: <CABPp-BEsJX8FiqYKwWsJ9+RHoZeOPG02Z0CFZHQXuKx9MAj45w@mail.gmail.com> (raw)
After a very long hiatus, git-filter-repo is again finally getting a
release. v2.45.0 is now available.
git filter-repo is a versatile tool for rewriting git repository
history. The public repo of filter-repo is at
https://github.com/newren/git-filter-repo
The tarballs can be found at:
https://github.com/newren/git-filter-repo/releases
git-filter-repo can also be installed via a variety of package managers
across Windows, Mac OS, or Linux (and maybe others)[1].
[1] https://github.com/newren/git-filter-repo/blob/master/INSTALL.md
----------------------------------------------------------------------
git-filter-repo 2.45 Release Notes
==================================
* Fixes:
* Work with git >= 2.43 (instead of immediately aborting with an error)
* Backward compatibility
* Do not create new replace references by default. Use the --replace-refs
option to change this, if wanted.
* Usability:
* Throw an error when users pass `--paths` instead of letting python
autocomplete to `--paths-from-file` (since users usually intended
to mean `--path`)
* Apply commit ID updates after the --message-callback
* Documentation:
* Update link to GitHub docs on purging data
* Miscellaneous:
* Add a --date-order option
* Cleanup callback scope
* Contrib scripts:
* [convert-svnexternals] fix parsing of wrongly transformed SVN revisions
* [lint-history] fix --refs option
* [clean-ignore] handle .gitignore exclusions
* [clean-ignore] do not require additional arguments to be passed
* [clean-ignore] support utf-8 filenames found in .gitignore files
Reply
Forward

Add reaction
reply other threads:[~2024-07-19 2:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-BEsJX8FiqYKwWsJ9+RHoZeOPG02Z0CFZHQXuKx9MAj45w@mail.gmail.com \
--to=newren@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.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;
as well as URLs for NNTP newsgroup(s).