From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Sergio <sergio.callegari@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: rsync a *bunch* of git repos
Date: Wed, 11 Jan 2012 10:52:30 -0600 [thread overview]
Message-ID: <4F0DBE4E.30401@gmail.com> (raw)
In-Reply-To: <loom.20120111T141805-791@post.gmane.org>
On 1/11/2012 7:22 AM, Sergio wrote:
>
> As an aside: git works fine when repos are transferred with rsync, but git packs
> are not rsync friendly nor friendly with backup strategies using binary deltas.
>
All these answers are assuming that your source git repos are quiet
during the rsync. If they are not quiet during the rsync then you are
going to need a more tailored rsync to do things in a certain order.
See this thread for details:
http://thread.gmane.org/gmane.comp.version-control.git/168699
v/r,
neal
next prev parent reply other threads:[~2012-01-11 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 21:15 rsync a *bunch* of git repos Jason
2012-01-10 21:24 ` Seth Robertson
2012-01-10 22:00 ` Philip Oakley
2012-01-10 22:30 ` Junio C Hamano
2012-01-11 13:22 ` Sergio
2012-01-11 16:52 ` Neal Kreitzinger [this message]
2012-01-24 14:11 ` Jason
2012-01-11 8:01 ` Andreas T.Auer
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=4F0DBE4E.30401@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--cc=sergio.callegari@gmail.com \
/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).