Taylor Blau <me@xxxxxxxxxxxx> writes:
> After (the rerolled version of) this series, we'll be in a state where:
>
> - `git multi-pack-index` will not run when outside of a Git
> repository.
> - The `--object-dir` argument will only recognize object directories
> belonging to an alternate of the current repository.
> - Using `--object-dir` to point to a repository which uses a
> different hash than the repository in the current working directory
> will continue to not work (as was the case before this series).
Hmph, re-reading the document for midx:
--object-dir=<dir>::
Use given directory for the location of Git objects. We check
`<dir>/packs/multi-pack-index` for the current MIDX file, and
`<dir>/packs` for the pack-files to index.
why does it matter if we are in a repository in the first place?
It's not like we combine the objects from the specified object dir
and our local object store (if that were the case, these two object
stores must be compatible).
How old is --object-dir option and how widely is it used? Can we
just remove it and have users go to the repository that uses it
as its object store with "git -C <there>" mechanism, or have we come
too far with this (apparently broken) design to make such a fix
infeasible?
Thanks.
