summaryrefslogtreecommitdiffstats
path: root/contrib/persistent-https
diff options
context:
space:
mode:
authorLucas Seiki Oshiro <lucasseikioshiro@gmail.com>2026-02-13 21:35:15 -0300
committerJunio C Hamano <gitster@pobox.com>2026-02-14 10:12:10 -0800
commitebb667add9b6be123b6eb6f4b9de636c83d6f30c (patch)
tree7afbb14a168bbe6d0a20c3d485d6c943cb11c3f1 /contrib/persistent-https
parent1faf5b085a171f9ba9a6d7a446e0de16acccb1dc (diff)
downloadgit-ebb667add9b6be123b6eb6f4b9de636c83d6f30c.tar.gz
git-ebb667add9b6be123b6eb6f4b9de636c83d6f30c.zip
repo: rename the output format "keyvalue" to "lines"
Both subcommands in git-repo(1) accept the "keyvalue" format. This format is newline-delimited, where the key is separated from the value with an equals sign. The name of this option is suboptimal though, as it is both too limiting while at the same time not really indicating what it actually does: - There is no mention of the format being newline-delimited, which is the key differentiator to the "nul" format. - Both "nul" and "keyvalue" have a key and a value, so the latter is not exactly giving any hint what makes it so special. - "keyvalue" requires there to be, well, a key and a value, but we want to add additional output that is only going to be newline delimited. Taken together, "keyvalue" is kind of a bad name for this output format. Luckily, the git-repo(1) command is still rather new and marked as experimental, so things aren't cast into stone yet. Rename the format to "lines" instead to better indicate that the major difference is that we'll get newline-delimited output. This new name will also be a better fit for a subsequent extension in git-repo(1). Helped-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https')
0 files changed, 0 insertions, 0 deletions