From: Eric Wong <e@80x24.org>
To: tools@linux.kernel.org
Subject: grokmirror: absolute paths and objstores..
Date: Tue, 11 Oct 2022 10:59:04 +0000 [thread overview]
Message-ID: <20221011105904.M713779@dcvr> (raw)
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.
reply other threads:[~2022-10-11 11:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221011105904.M713779@dcvr \
--to=e@80x24.org \
--cc=tools@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).