git clone --bundle-uri: provide progress feedback?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: git@xxxxxxxxxxxxxxx
- Subject: git clone --bundle-uri: provide progress feedback?
- From: Xavier Morel <xmo@xxxxxxxx>
- Date: Fri, 11 Apr 2025 13:07:28 +0200
- User-agent: Mozilla Thunderbird
I've been looking at `--bundle-uri` for a repository of some size (~5
million objects, ~10GB fresh cloned though an aggressive gc get it down
to under 2), however from a UX perspective it seems to have a bit of an
issue: while normally `git clone` provides pretty extensive progress
feedback as far as I can see there is no feedback whatsoever while
`clone` is interacting with the bundle, even explicitly setting
`--verbose` and `--progress`, at least when the bundle is a local file.
I assume bundle-uri is mostly intended for large repositories, for which
even a clone with a bundle uri can take a while, and the lack of any
sort of feedback until git reaches out to the actual repository to find
what was not in the bundle is somewhat distressing.
And side-note, it might make sense to emit a warning when trying to
combine `--bundle-uri` with `--filter`? I assume if any filtering
happens it happens only on the reconciliation fetch, which should be
extremely small compared to the bundle's size. Experimentally with a
sample size of (1) using `--filter=tree:0` with a bundle uri yields a
larger repository *and* is slower than leaving the filter out.
[Index of Archives]
[Linux Kernel Development]
[Gcc Help]
[IETF Annouce]
[DCCP]
[Netdev]
[Networking]
[Security]
[V4L]
[Bugtraq]
[Yosemite]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Linux SCSI]
[Fedora Users]