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

Re: [PATCH] Improve documentation of git-filter-branch rev-list specification.

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Nov 21, 2007, 07:49 UTC
Message-ID
<4743E309.4090707@viscovery.net>
In-Reply-To
<877ikc3gzc.wl%cworth@cworth.org>
Carl Worth schrieb:
Show 7 quoted lines
> +The filters can modify the tree content stored in each commit,
> +(e.g. removing a file or running a perl rewrite on all files), or the
> +associated information about each commit, (commit message, author,
> +parent, etc.). Any information not affected by a filter (including
> +original commit times or merge information) will be preserved. If you
> +specify no filters, the commits will be recommitted without any
> +changes.

"... will be recommitted without any changes as long as no grafted parents are encountered. Any grafted parents will be written into the commits even if no filters are specified."

-- Hannes
Previous: Johannes Schindelin
Message 4 of 4 in “Improve documentation of git-filter-branch rev-list specification.”
  1. Improve documentation of git-filter-branch rev-list specification.Carl Worth, Nov 20, 2007
  2. Ideas for improving the filter-branch workflowCarl Worth, Nov 20, 2007
  3. Johannes SchindelinNov 20, 2007
  4. Johannes SixtNov 21, 2007

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.