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

Re: filter-branch IO optimization

From
Johannes Sixt <j6t@kdbg.org>
Date
Oct 11, 2012, 18:36 UTC
Message-ID
<5077119E.4060702@kdbg.org>
In-Reply-To
<fa1e05a5-54b3-47ff-bd28-dc463ebbc4bd@zcs>
Am 11.10.2012 17:39, schrieb Enrico Weigelt:
> The main goal of this filtering is splitting out many modules from a
> large upstream repo into their own downstream repos.
...
> The next step I have in mind is using --subdirectory-filter, but open
> questsions are:
> 
> * does it suffer from the same problems w/ empty username/email like --tree-filter ?
I think so.
> ** if yes: what can I do about it (have an additional pass for fixing that before
>    running the --tree-filter ?
Use --env-filter.
> * can I somehow teach the --subdirectory filter to place the result under some
>   somedir instead of directly to root ?
No, but see the last example in the man page.
> * can I use --tree-filter in combination with --subdireectory-filter ? 
>   which one is executed first ?
Yes. --subdirectory-filter applies first.
-- Hannes
Previous: Enrico WeigeltNext: Thomas Rast
Message 2 of 7 in “filter-branch IO optimization”
  1. Enrico WeigeltOct 11, 2012
  2. Johannes SixtOct 11, 2012
  3. Thomas RastOct 11, 2012
  4. Enrico WeigeltOct 12, 2012
  5. Enrico WeigeltOct 12, 2012
  6. Enrico WeigeltOct 12, 2012
  7. Jeff KingOct 12, 2012

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.