git/Documentation/technical/bundle-format.txt, branch v2.35.2Mirror of https://git.kernel.org/pub/scm/git/git.git/
https://git.shady.money/git/atom?h=v2.35.22020-07-30T16:16:48Zbundle: add new version for use with SHA-2562020-07-30T16:16:48Zbrian m. carlsonsandals@crustytoothpaste.net2020-07-29T23:14:20Zurn:sha1:c5aecfc8669b9c56fd1ba31356eedc37b7289f9c
Currently we detect the hash algorithm in use by the length of the
object ID. This is inelegant and prevents us from using a different
hash algorithm that is also 256 bits in length.
Since we cannot extend the v2 format in a backward-compatible way, let's
add a v3 format, which is identical, except for the addition of
capabilities, which are prefixed by an at sign. We add "object-format"
as the only capability and reject unknown capabilities, since we do not
have a network connection and therefore cannot negotiate with the other
side.
For compatibility, default to the v2 format for SHA-1 and require v3
for SHA-256.
In t5510, always use format v3 so we can be sure we produce consistent
results across hash algorithms. Since head -n N lists the top N lines
instead of the Nth line, let's run our output through sed to normalize
it and compare it against a fixed value, which will make sure we get
exactly what we're expecting.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
doc: describe Git bundle format2020-02-07T20:47:02ZMasaya Suzukimasayasuzuki@google.com2020-02-07T20:42:25Zurn:sha1:7378ec90e1c59610dfcac8a4bce7a9d29681380d
The bundle format was not documented. Describe the format with ABNF and
explain the meaning of each part.
Signed-off-by: Masaya Suzuki <masayasuzuki@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>