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

Re: git-filter-branch behavior

From
Jonathan Nieder <jrnieder@uchicago.edu>
Date
Aug 13, 2008, 21:00 UTC
Message-ID
<Pine.GSO.4.62.0808131552130.11537@harper.uchicago.edu>
In-Reply-To
<Pine.GSO.4.62.0808131533320.10800@harper.uchicago.edu>
Jonathan Nieder wrote:
> # prune-empty-commits - filter-branch filter to avoid boring commits
> #
> # Usage: git-filter-branch --tree-filter <something> \
> # 		--commit-filter 'prune-empty-commits "$@"' -- <refs>
[...]
> 	map "$sha1" | while read parent

Oops - the 'map' function is not passed on to scripts, so one should use this script with "--commit-filter '. prune-empty-commits'".

> 	test "-n interesting" && break
s/"-n interesting"/-n "$interesting"/
Sorry about that.
Previous: Jonathan NiederNext: Michael J Gruber
Message 3 of 4 in “git-filter-branch behavior”
  1. David NeuAug 13, 2008
  2. Jonathan NiederAug 13, 2008
  3. Jonathan NiederAug 13, 2008
  4. Michael J GruberAug 15, 2008

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.