git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	git-packagers@googlegroups.com
Subject: [ANNOUNCE] git-filter-repo v2.27.0 (Was: Re: [ANNOUNCE] Git v2.27.0)
Date: Mon, 1 Jun 2020 10:08:06 -0700	[thread overview]
Message-ID: <CABPp-BF+xvzroi5QU8zPp-7KoSS16v1CsM43vWx1WO5NjyU0BQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqzh9mu4my.fsf@gitster.c.googlers.com>

Hi,

On Mon, Jun 1, 2020 at 9:37 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> The latest feature release Git v2.27.0 is now available at the
> usual places.  It is comprised of 537 non-merge commits since
> v2.26.0, contributed by 71 people, 19 of which are new faces.

The latest release of git-filter-repo, v2.27.0, is also now available.
It is comprised of 26 non-merge commits since v2.26.0, including two
changes from new contributors.

If you have been holding off on trying filter-repo because you didn't
want to figure out how to convert your filter-branch or BFG commands,
there are now cheat sheets for converting any example from the manual of
either of those tools into equivalent filter-repo commands; see the last
two links here:

    https://github.com/newren/git-filter-repo#how-do-i-use-it


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].

New contributors whose contributions weren't in v2.26.0 are as follows.
Welcome to the git-filter-repo development community!

  * Kate F
  * Marius Renner

[1] https://github.com/newren/git-filter-repo/blob/master/INSTALL.md

----------------------------------------------------------------

git-filter-repo 2.27 Release Notes
==================================

(Note: Additional information is available for many release notes at
    https://github.com/newren/git-filter-repo/issues/<NUMBER>)

* Fixes:
  * fix ugly bug with mixing path filtering and renaming (#96)
  * suggest --no-local when cloning local repos (discourage use of --force)
  * fix possible deadlock in sanity_check_args (#86)
  * fix --prune-degenerate=never with path filtering (#92)
  * throw an error if user specifies any path starting with a slash (#73)
  * ensure we write final newline after final progress update (#84)
  * repack with --source or --target (#66)
  * make --version more robust against modified shebangs
  * make git version requirement error message more direct (#94)
  * allow removing .git directories from history

* Documentation:
  * fix typo in example (#69)
  * add more detailed explanation of safety checks and --force
  * add guides & cheat sheets for people converting from filter-branch or BFG
  * add examples for --subdirectory-filter and --to-subdirectory-filter
  * add missing documentation for --no-ff option (#92)
  * add more --paths-from-file examples with large filtering lists
  * clarify usage of --use-base-name
  * streamline install instructions a bit
  * and various other miscellaneous improvements and fixes

* contrib scripts:
  * fix special character handling in filter-lamely (#71)

* Miscellaneous:
  * add sanity checks around release script


Changes since v2.26.0 are as follows:

Elijah Newren (24):
      Makefile: a few sanity checks for releasing
      filter-repo: fix bitrotted documentation links
      filter-repo: suggest --no-local when cloning local repos
      filter-repo: ensure we write final newline after final progress update
      filter-repo: make --version more robust against modified shebangs
      filter-repo: clarify usage of --use-base-name
      git-filter-repo.txt: add examples for --[to-]subdirectory-filter
      filter-repo: throw an error if user specifies any path starting
with a slash
      git-filter-repo.txt: add documentation of --no-ff option
      filter-repo: allow removing .git directories from history
      Documentation: add guides for people converting from filter-branch or BFG
      git-filter-repo.txt: add more --paths-from-file examples with
large filtering lists
      INSTALL: streamline a bit and guide folks to package managers
      filter-repo: fix --no-local error when there is no remote
      Documentation: add more detailed explanation of safety checks and --force
      filter-repo: make git version requirement error message more direct
      filter-repo: fix possible deadlock in sanity_check_args
      filter-repo: fix ugly bug with mixing path filtering and renaming
      filter-repo: fix --prune-degenerate=never with path filtering
      git-filter-repo.txt: fix extraneous space
      filter-repo: repack with --source or --target
      filter-repo (README): link cheat sheets from usage section too
      filter-repo (README): separate sections for different tools
      git-filter-repo.txt: connect --no-local and fresh clones more thoroughly

Kate F (1):
      git-filter-repo.txt: Fix typo for example

Marius Renner (1):
      contrib: fix special character handling in filter-lamely

  reply	other threads:[~2020-06-01 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 16:34 [ANNOUNCE] Git v2.27.0 Junio C Hamano
2020-06-01 17:08 ` Elijah Newren [this message]
2020-06-23 16:16   ` [ANNOUNCE] git-filter-repo v2.27.1 Elijah Newren

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABPp-BF+xvzroi5QU8zPp-7KoSS16v1CsM43vWx1WO5NjyU0BQ@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).