On Fri, Feb 09, 2018 at 09:05:00PM +0100, Ævar Arnfjörð Bjarmason wrote: > >> diff --git a/t/t5510-fetch.sh b/t/t5510-fetch.sh > >> @@ -548,18 +548,52 @@ set_config_tristate () { > >> *) > >> git config "$1" "$2" > >> + key=$(echo $1 | sed -e 's/^remote\.origin/fetch/') > > > > Faster (thus more Windows-friendly) assuming that $1 always starts > > with "remote.origin": > > > > key=fetch${u#remote.origin} > > Tests fail with this and I'm not excited to be the first user in git's > test suite to use some novel shell feature, no existing uses of > ${u[...]. > > I also think stuff like this is on the wrong side of cleverness > v.s. benefit. I can't find any reference to this syntax in bash or dash > manpages (forward-search "${u"), but echo | sed is obvious, and it's not > going to make a big difference for Windows. The "u" isn't the magic, it's the "#". I.e.: key=fetch${1#remote.origin} and it's used all over the place in our scripts. I'm not sure why Eric wrote "u". :) -Peff