git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Farina <drfarina@gmail.com>
To: git@vger.kernel.org
Subject: backup or mirror a repository
Date: Thu, 27 Sep 2007 12:35:42 -0700	[thread overview]
Message-ID: <1190921742.2263.17.camel@Tenacity> (raw)

Hello list,

I have been poking around on IRC and gmane, but haven't yet seen a
solution to my problem:

What I really want is something semantically identical to a recursive
copy of my entire git repository on one machine sent to another machine.
Right now I can't simply use "rsync -ar --delete ..." because the pack
changes names, thus fooling rsync and sending a bunch of bits over the
network.

I saw git-mirror on gmane and asked around in IRC, but the former seems
to have died sometime last November and the latter told me I'd probably
have to write some glue to process git show-ref and git ls-remote. This
seems viable, but suboptimal. Another user chimed in that they also had
the same use case as myself.


fdr

(Justifications: I am super paranoid, so I want to push my local
branches to another disk to be safe, but then they proliferate over time
since deleted local branches are not also deleted on the target
repository. I also want to work on multiple machines seamlessly, and as
such doing a bunch of "git checkout -r ..." when I need to change
branches is also suboptimal. As I said, I can get what I want by simply
using rsync, so this is entirely about efficiency by exploiting git's
structure)

             reply	other threads:[~2007-09-27 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 19:35 Dan Farina [this message]
2007-09-27 21:56 ` backup or mirror a repository Johannes Schindelin
2007-09-28  0:51   ` Dan Farina
2007-09-28  1:56     ` Johannes Schindelin
2007-09-28  2:37       ` Dan Farina
2007-09-28  6:27         ` Junio C Hamano
2007-09-28  7:20           ` Dan Farina
2007-10-18  5:32           ` Dmitry Potapov
2007-10-30  0:33             ` Johannes Schindelin

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=1190921742.2263.17.camel@Tenacity \
    --to=drfarina@gmail.com \
    --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.
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 NNTP newsgroup(s).