3 messages, 3 authors, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:27
Mark Levedahl [off-list ref] writes:
+ printf "$mandir/%s\n" $(git ls-tree -r --name-only $head) | xargs gzip -f
No risk that ls-tree output is too long to fit within the exec args limit to run printf?
From: René Scharfe <hidden>
Date: 2016-06-15 22:43:28
Junio C Hamano schrieb:
Mark Levedahl [off-list ref] writes:quoted
+ printf "$mandir/%s\n" $(git ls-tree -r --name-only $head) | xargs gzip -fNo risk that ls-tree output is too long to fit within the exec args limit to run printf?
Perhaps this instead? git ls-tree -r --name-only $head | (cd "$mandir" && xargs gzip -f) René
From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:43:28
Hi, On Tue, 7 Aug 2007, Ren? Scharfe wrote:
Junio C Hamano schrieb:quoted
Mark Levedahl [off-list ref] writes:quoted
+ printf "$mandir/%s\n" $(git ls-tree -r --name-only $head) | xargs gzip -fNo risk that ls-tree output is too long to fit within the exec args limit to run printf?Perhaps this instead? git ls-tree -r --name-only $head | (cd "$mandir" && xargs gzip -f)
I would have done git ls-tree -r --name-only $head | sed "s|^|$mandir|" | xargs gzip -f but I like your version better. Thanks for teaching me, Dscho