summaryrefslogtreecommitdiffstats
path: root/contrib/persistent-https
diff options
context:
space:
mode:
authorKristoffer Haugsbakk <code@khaugsbakk.name>2026-01-08 07:28:20 +0100
committerJunio C Hamano <gitster@pobox.com>2026-01-09 06:08:37 -0800
commit3f051fc9c9f9e719ad0e37b66737b466b82d17b3 (patch)
tree251041fd88b0f4bc4368161099ac0bfd2542f7f1 /contrib/persistent-https
parent89d4f3af16a95fe1b6abe8c9f43fb7fb6826dadf (diff)
downloadgit-3f051fc9c9f9e719ad0e37b66737b466b82d17b3.tar.gz
git-3f051fc9c9f9e719ad0e37b66737b466b82d17b3.zip
doc: patch-id: --verbatim locks in --stable
The default `--unstable` is a legacy format that predates `--stable`. That’s why 2871f4d4 (builtin: patch-id: add --verbatim as a command mode, 2022-10-24) made `--verbatim` lock in[1] `--stable`: Users of --unstable mainly care about compatibility with old git versions, which unstripping the whitespace would break. Thus there isn't a usecase for the combination of --verbatim and --unstable, and we don't expose this so as to not add maintainence burden. † 1: imply `--stable`, disallow `--unstable` Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https')
0 files changed, 0 insertions, 0 deletions