git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Dennis Putnam <dap1@bellsouth.net>,  git@vger.kernel.org
Subject: Re: Migrating Repository without Network
Date: Tue, 21 Oct 2025 15:23:33 -0700	[thread overview]
Message-ID: <xmqqo6pzsxlm.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CAKBB=MRUBSv-_pqWuUgi6d1+o_X=iq-fLzfSkCYMaiPw@mail.gmail.com> (D. Ben Knoble's message of "Tue, 21 Oct 2025 17:23:38 -0400")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

> On Tue, Oct 21, 2025 at 10:52 AM Dennis Putnam <dap1@bellsouth.net> wrote:
>>
>> I have a server with a git repository whose NIC is no longer working. I
>> need to migrate that repository to a new server using a flash drive. I
>> can only find instructions for migrating when both servers have network
>> access. Can someone tell me how to do a migration without using a
>> network? TIA.
>
> Have a look at git-bundle(1), which was designed for something similar
> to this use case I believe. Or, rsync the repo to the flash drive and
> then off?

But bundle is only about preserving/transporting the history
recorded in the repository.  It does not do the repository config or
the hooks.  Those folks would want to migrate the entire repository
data off of a failing server, so I think "rsync/cp" would be the
more sensible route.

Thanks.


  reply	other threads:[~2025-10-21 22:23 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 [this message]
2025-10-22  9:04   ` Konstantin Khomoutov
2025-10-22  9:14     ` Konstantin Khomoutov
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=xmqqo6pzsxlm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --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).