summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-remote-explicit
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2020-11-06 13:56:24 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-11-09 17:44:41 -0800
commit3baf58bfb4bcfe201970abeffa8e1396d2324250 (patch)
tree2ea7148e16c6689322c0ec404e16d21a136d2439 /t/t5515/fetch.br-remote-explicit
parentGit 2.29.2 (diff)
downloadtgif-3baf58bfb4bcfe201970abeffa8e1396d2324250.tar.xz
format-patch: make output filename configurable
For the past 15 years, we've used the hardcoded 64 as the length limit of the filename of the output from the "git format-patch" command. Since the value is shorter than the 80-column terminal, it could grow without line wrapping a bit. At the same time, since the value is longer than half of the 80-column terminal, we could fit two or more of them in "ls" output on such a terminal if we allowed to lower it. Introduce a new command line option --filename-max-length=<n> and a new configuration variable format.filenameMaxLength to override the hardcoded default. While we are at it, remove a check that the name of output directory does not exceed PATH_MAX---this check is pointless in that by the time control reaches the function, the caller would already have done an equivalent of "mkdir -p", so if the system does not like an overly long directory name, the control wouldn't have reached here, and otherwise, we know that the system allowed the output directory to exist. In the worst case, we will get an error when we try to open the output file and handle the error correctly anyway. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-remote-explicit')
0 files changed, 0 insertions, 0 deletions