partial clone filter tree:0 appears to be a terrible choice for the zephyr repository

Hi,

As a long time git user, I was recently very confused when I attempted to (for example)

git log zephyr/tests/kernel/common/src/atomic.c

or

gitk zephyr/tests/kernel/common/src/atomic.c

and found my machine crawling along at close to 0 kilometers per hour (I usually say miles per hour--same idea).

Some initial googling gave me the WRONG answer--suggesting I was witnessing a Windows issue--so I switched to Linux and found the same problem.

More googling and testing revealed that this was an issue with the use of tree:0 partial clone filtering. You can see that in zephyr/.git/config that has the statement

partialclonefilter = tree:0

I believe that one can also get good results by using the blob filtering

git clone --filter=blob:none ...

Please show me how you or I can fix this in the scripts or when using VS Code. I know that zephyr is not the immediate code of my project, but I do find this limitation a ridiculous annoyance. Thanks.

Burt Silverman

Parents Reply Children
No Data
Related