summaryrefslogtreecommitdiff
path: root/Documentation/gitdiffcore.txt
diff options
context:
space:
mode:
authorLibravatar Eric Wong <e@80x24.org>2021-02-10 21:55:43 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-02-10 14:24:13 -0800
commita5cdca452052e824c9f3f7cf78385fbec5bb1976 (patch)
tree9bf24ae7ec5a100882ff80ac2639b822f783dbc6 /Documentation/gitdiffcore.txt
parentGit 2.30.1 (diff)
downloadtgif-a5cdca452052e824c9f3f7cf78385fbec5bb1976.tar.xz
t1500: ensure current --since= behavior remains
This behavior of git-rev-parse is observed since git 1.8.3.1 at least(*), and likely earlier versions. At least one git-reliant project in-the-wild relies on this current behavior of git-rev-parse being able to handle multiple --since= arguments without squeezing identical results together. So add a test to prevent the potential for regression in downstream projects. (*) 1.8.3.1 the version packaged for CentOS 7.x Signed-off-by: Eric Wong <e@80x24.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/gitdiffcore.txt')
0 files changed, 0 insertions, 0 deletions