From: Jeff King <peff@peff.net>
To: Neal Kreitzinger <nkreitzinger@gmail.com>
Cc: Neal Kreitzinger <neal@rsss.com>, git@vger.kernel.org
Subject: Re: rsync busy non-bare git repo 'source' to quiet
Date: Tue, 8 Mar 2011 17:38:41 -0500 [thread overview]
Message-ID: <20110308223841.GA6648@sigill.intra.peff.net> (raw)
In-Reply-To: <4D76ABB1.9080001@gmail.com>
On Tue, Mar 08, 2011 at 04:20:33PM -0600, Neal Kreitzinger wrote:
> Rsync seems like a simpler solution and more accurate solution for
> creating a copy of an ecosystem of interrelated git repos colocated on
> the same box.
Sure. It is simpler, but not atomic unless you do a multi-stage rsync.
> A previous post in the newsgroup states:
> > If you want your rsync backup to be fine, you need to follow some
> >ordering. You need to copy the refs first (.git/packed-refs and
> >.git/refs/), then the loose objects (.git/objects/??/*), and then all
> >the rest. If files are copied in a different order while some write
> >operations are performed on the source repository then you may end up
> >with an incoherent repository."
>
> Would that work?
If you do it in that order, the end result will be a consistent repo.
But during the copy, the refs at the destination will point to objects
you don't have. I don't know if that matters for your case.
-Peff
next prev parent reply other threads:[~2011-03-08 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 21:25 rsync busy non-bare git repo 'source' to quiet Neal Kreitzinger
2011-03-08 21:39 ` Jeff King
2011-03-08 22:20 ` Neal Kreitzinger
2011-03-08 22:38 ` Jeff King [this message]
2011-03-08 23:00 ` Neal Kreitzinger
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=20110308223841.GA6648@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=neal@rsss.com \
--cc=nkreitzinger@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).