summaryrefslogtreecommitdiff
path: root/t/t4018/php-function
diff options
context:
space:
mode:
authorLibravatar Taylor Blau <me@ttaylorr.com>2018-10-08 11:09:30 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-10-09 14:30:03 +0900
commit40f327faf543ccaeb03aa0362f3fed7438c2c615 (patch)
tree1bd7c4249a970e8f0a2bc1708519a930f7f3e16d /t/t4018/php-function
parenttransport.c: introduce core.alternateRefsCommand (diff)
downloadtgif-40f327faf543ccaeb03aa0362f3fed7438c2c615.tar.xz
transport.c: introduce core.alternateRefsPrefixes
The recently-introduced "core.alternateRefsCommand" allows callers to specify with high flexibility the tips that they wish to advertise from alternates. This flexibility comes at the cost of some inconvenience when the caller only wishes to limit the advertisement to one or more prefixes. For example, to advertise only tags, a caller using 'core.alternateRefsCommand' would have to do: $ git config core.alternateRefsCommand ' \ f() { git -C "$1" for-each-ref \ refs/tags --format="%(objectname)" }; f "$@"' The above is cumbersome to write, so let's introduce a "core.alternateRefsPrefixes" to address this common case. Instead, the caller can run: $ git config core.alternateRefsPrefixes 'refs/tags' Which will behave identically to the longer example using "core.alternateRefsCommand". Since the value of "core.alternateRefsPrefixes" is appended to 'git for-each-ref' and then executed, include a "--" before taking the configured value to avoid misinterpreting arguments as flags to 'git for-each-ref'. In the case that the caller wishes to specify multiple prefixes, they may separate them by whitespace. If "core.alternateRefsCommand" is set, it will take precedence over "core.alternateRefsPrefixes". Signed-off-by: Taylor Blau <me@ttaylorr.com> Acked-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4018/php-function')
0 files changed, 0 insertions, 0 deletions