git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] filter-branch: Fix error message for --prune-empty --commit-filter

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Feb 8, 2010, 10:10 UTC
Message-ID
<4B6FE325.5000909@drmicha.warpmail.net>
In-Reply-To
<1265596681-10561-1-git-send-email-jacob.helwig@gmail.com>
Jacob Helwig venit, vidit, dixit 08.02.2010 03:38:
> Running filter-branch with --prune-empty and --commit-filter, no longer
> incorrectly reports that you had tried to run '--filter-commit' in
> combination with '--prune-empty'.
In order to understand this sentence, I had to look twice at the patch text.

What's going on is that that typo was there from the beginning, right? (Induced from the name of a script variable, I see.) How about:

Running filter-branch with --prune-empty and --commit-filter reports "Cannot set --prune-empty and --filter-commit at the same time".

Change it to use the correct name "--commit-filter" of the option.
Show 21 quoted lines
> Signed-off-by: Jacob Helwig <jacob.helwig@gmail.com>
> ---
> 
> Sorry for the re-send.  Forgot the SOB...
> 
>  git-filter-branch.sh |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/git-filter-branch.sh b/git-filter-branch.sh
> index e95845c..88fb0f0 100755
> --- a/git-filter-branch.sh
> +++ b/git-filter-branch.sh
> @@ -207,7 +207,7 @@ t,)
>  ,*)
>  	;;
>  *)
> -	die "Cannot set --prune-empty and --filter-commit at the same time"
> +	die "Cannot set --prune-empty and --commit-filter at the same time"
>  esac
>  
>  case "$force" in
Previous: Jacob HelwigNext: Jacob Helwig
Message 3 of 4 in “filter-branch: Fix error message for --prune-empty --commit-filter”
  1. filter-branch: Fix error message for --prune-empty --commit-filterJacob Helwig, Feb 8, 2010
  2. filter-branch: Fix error message for --prune-empty --commit-filterJacob Helwig, Feb 8, 2010
  3. Michael J GruberFeb 8, 2010
  4. filter-branch: Fix error message for --prune-empty --commit-filterJacob Helwig, Feb 12, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.