{"thread":{"id":"14991","subject":"Why is 'map' used in filter-branch's skip_commit?","startedAt":"2008-08-13T21:16:27Z","lastAt":"2008-08-13T21:16:27Z","messageCount":1,"participants":["Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"87107","messageId":"Pine.GSO.4.62.0808131606020.11830@harper.uchicago.edu","threadId":"14991","inReplyTo":null,"subject":"Why is 'map' used in filter-branch's skip_commit?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@uchicago.edu","sentAt":"2008-08-13T21:16:27Z","receivedAt":"2008-08-13T21:16:27Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nI was wondering why skip_commit uses 'map' to rewrite the parents\nsupplied to the commit-filter.\n\nFor a moment, I was worried that if skip_commit has to rewrite parents\nthen the user should have to, too, before passing them to git\ncommit-tree - but no, it seems that the parents supplied to the\ncommit-filter are already rewritten.  In fact, before skip_commit was\nintroduced (commit f95eef), an example in the filter-branch\ndocumentation used 'echo' instead of 'map' for the same construct.\n\nIs it just a matter of style?  Or am I missing something else?\n\nThanks,\n\nJonathan\n"}]}