* grokmirror: absolute paths and objstores..
@ 2022-10-11 10:59 Eric Wong
0 siblings, 0 replies; only message in thread
From: Eric Wong @ 2022-10-11 10:59 UTC (permalink / raw)
To: tools
One thing I noticed with grokmirror is that it uses absolute
paths everywhere. That makes it non-trivial to relocate the repos
to a different FS location (e.g.: clone on my workstation while
on a fast network, copy to USB stick, copy to laptop, and work
offline)
I also wonder if using only URLs (and not FS paths) remote.*.url
in both objstores and non-objstores would be simpler and more
robust. In that case, `git fetch --all' can be called from the
objstores to update all remotes.
The non-objstores would only store refs in nearly all cases.
That would completely avoid local FS paths from being in
$GIT_DIR/config, only objects/info/alternates
A lazy implementor can just call `git fetch' on the non-objstore
and let alternates + repack deal with redundancy in case there's
a small window where commits appear after the objstore fetch
but before the non-objstore fetch.
An implementor can of course avoid `git fetch' on non-objstores
by manually updating refs in the non-objstore, though.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-10-11 11:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-10-11 10:59 grokmirror: absolute paths and objstores Eric Wong
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.