list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Daniel Höpfl" <>
Subject: Suppressing filter-branch warning
Date: Fri, 6 Nov 2020 10:04:43 +0100	[thread overview]
Message-ID: <> (raw)

Hello there,

What did you do before the bug happened? (Steps to reproduce your issue)
git filter-branch -f --env-filter '' --tag-name-filter cat -- HEAD

What did you expect to happen? (Expected behavior)
See below (difference).

What happened instead? (Actual behavior)
When using git filter-branch, the following message is shown:

WARNING: git-filter-branch has a glut of gotchas generating mangled history
         rewrites.  Hit Ctrl-C before proceeding to abort, then use an
         alternative filtering tool such as 'git filter-repo'
         ( instead.  See the
         filter-branch manual page for more details; to squelch this warning,

You can suppress this by setting the environment variable shown.

What's different between what you expected and what actually happened?

Normally, when git introduces this kind of change, there is a
git config variable that one can set to suppress it.
That way one has fine grade control when to suppress it (one repo only...globally).

Anything else you want to add:


Please review the rest of the bug report below.
You can delete any lines you don't wish to share.

[System Info]
git version:
git version 2.29.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64
compiler info: gnuc: 8.3
libc info: glibc: 2.28
$SHELL (typically, interactive shell): /bin/bash

             reply	other threads:[~2020-11-06  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  9:04 Daniel Höpfl [this message]
2020-11-06 18:06 ` Junio C Hamano
2020-11-06 20:12   ` Elijah Newren
2020-11-10 11:21     ` Daniel Höpfl
2020-11-10 12:15       ` Johannes Schindelin

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:

  List information:

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

  git send-email \ \ \ \
    --subject='Re: Suppressing filter-branch warning' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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