Elijah Newren

I added a --file-info-callback as part of commit 615720731589 (filter-repo: add a --file-info-callback, 2024-10-23). That commit adds a callback which allows you to work with both the filename and file...

Yeah, working as expected. Unfortunately, attempting to determine if the new pathnames are in the commit history, within a relevant range of commits, is computationally quite expensive and can become...

> and if the analysis could show that info it'd really help with finding big non-LFS'd blobs Note that --analyze currently only reports sizes in git history, not in external...

Ooh, this is interesting; I haven't seen one of these before. We've had lots of reports of failure to lock refs, but always with branch/tag names, never the pack-refs file....

> > * What are all the refs in this repository (i.e. output from `git show-ref`)? > > there's a LOT of refs, so I won't copy-paste the output here....

So, after a bit of digging: ``` fatal: failed to run pack-refs ``` This comes from the gc step: ``` $ git grep 'failed to run %s' builtin/gc.c:#define FAILED_RUN "failed...

> > an ill-timed simultaneous git process of some sort running in the repo while it was trying to repack > > what might lead to this? I know that...

You haven't stated what the repository structure of the original repository was. I suspect that `Server/Web/Amagno.Server.Web.DocumentRecognition/` was not a directory tracked within git; perhaps you gave a path relative to...

No response, so I'll close.

Thanks for sending in a suggestion for the docs; very much appreciated. While you raise a valid point, I am concerned that the suggestion might only be applicable in special...