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

Why is 'map' used in filter-branch's skip_commit?

From
Jonathan Nieder <jrnieder@uchicago.edu>
Date
Aug 13, 2008, 21:16 UTC
Message-ID
<Pine.GSO.4.62.0808131606020.11830@harper.uchicago.edu>
Hi,

I was wondering why skip_commit uses 'map' to rewrite the parents supplied to the commit-filter.

For a moment, I was worried that if skip_commit has to rewrite parents then the user should have to, too, before passing them to git commit-tree - but no, it seems that the parents supplied to the commit-filter are already rewritten. In fact, before skip_commit was introduced (commit f95eef), an example in the filter-branch documentation used 'echo' instead of 'map' for the same construct.

Is it just a matter of style?  Or am I missing something else?
Thanks,
Jonathan
Message 1 of 1 in “Why is 'map' used in filter-branch's skip_commit?”
  1. Jonathan NiederAug 13, 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.