From: Konstantin Khomoutov <kostix@bswap.ru>
To: Dennis Putnam <dap1@bellsouth.net>
Cc: git@vger.kernel.org
Subject: Re: Migrating Repository without Network
Date: Wed, 22 Oct 2025 12:14:48 +0300 [thread overview]
Message-ID: <yfg4ow3ndckqr6zvrbvldbynv2jgaf5ip76phusdtiwelnz4e2@5e5hct2uujo5> (raw)
In-Reply-To: <6tygbwc6ifpuo3xylsmsveufqyroazy35u4lyblnvuls3l7n3u@d4ail3s6vtoa>
On Wed, Oct 22, 2025 at 12:04:15PM +0300, Konstantin Khomoutov wrote:
[...]
> In either case, it will be possible to fetch all the data from the repo
> saved on the flash drive: it might be not exactly obvious but all Git
> commands which fetch data - such as "clone", "fetch" etc - do understand
> "plain" pathnames such as /the/path/to/the/repo and URLs with the special
> scheme "file://" - such as file:///the/path/to/the/repo, allowing them to
> work with on-disk repos available locally such as on a mounted flash drive.
...it should be noted, though, that "normal" and "bare" repository have
different schemes of storing branches available in them, and it might affect
the approach you will need to employ to fetch really *all* the data to form a
new repo.
It's hardly possible to dive further in this topic because we have next to
zero knowledge about your setup - including whether that repo is bare and is
accessed from the outside, or normal and merely shared between the users
physically logged into the server and so on. I mean, it may so happen that all
you will need to do is to copy the repo to a flash drive and then copy it
again to the new server, possibly fix filesystem permissions on it so that
they match the ones the old repo has, and call it a day. In case you will need
more advanced help, you'll need to provide more details on your situation.
next prev parent reply other threads:[~2025-10-22 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94497aac-c61a-4b17-9e4c-8ca9b966829c.ref@bellsouth.net>
2025-10-21 14:21 ` Migrating Repository without Network Dennis Putnam
2025-10-21 21:23 ` D. Ben Knoble
2025-10-21 22:23 ` Junio C Hamano
2025-10-22 9:04 ` Konstantin Khomoutov
2025-10-22 9:14 ` Konstantin Khomoutov [this message]
2025-10-22 15:29 ` Dennis Putnam
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yfg4ow3ndckqr6zvrbvldbynv2jgaf5ip76phusdtiwelnz4e2@5e5hct2uujo5 \
--to=kostix@bswap.ru \
--cc=dap1@bellsouth.net \
--cc=git@vger.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).