diff options
| author | Patrick Steinhardt <ps@pks.im> | 2026-08-05 09:44:47 +0200 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2026-08-05 09:42:50 -0700 |
| commit | 8a51f6e8c5e1e1b849f41069dabc7bdfc1177d9b (patch) | |
| tree | b2959be7201b66ef88ad63fbdbd47b97847b7f63 /t/t4013/diff.diff_initial..side | |
| parent | 726782254239706bc91276537450b7a21b81f99e (diff) | |
odb/streaming: support streaming arbitrary object types
The object database supports the ability to write object streams into
it. This functionality is used when we encounter a blob that is larger
than "core.bigFileThreshold" so that we don't have to soak large files
into memory.
As we only ever write large files, the infrastructure doesn't support
specifying any other object type than "blob". This limitation is quite
artificial though: there is no reason why we shouldn't support writing
arbitrary large objects with a stream. While it's very unlikely that we
encounter a huge object other than a blob, users are known to be
creative and sometimes like to inflict pain on themselves by creating
commits or trees that are huge.
Extend the infrastructure to support streaming arbitrary object types.
For now we don't use this functionality anywhere, but it brings us a bit
closer to unify `struct odb_read_stream` and `struct odb_write_stream`.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.diff_initial..side')
0 files changed, 0 insertions, 0 deletions
