From: "Neal Kreitzinger" <neal@rsss.com>
To: git@vger.kernel.org
Subject: rsync busy non-bare git repo 'source' to quiet
Date: Tue, 8 Mar 2011 15:25:00 -0600 [thread overview]
Message-ID: <il66rd$46u$1@dough.gmane.org> (raw)
Does anyone have an example of an rsync bash script that will make a good
copy of a non-bare git repo (including the working tree) while the "source"
git repo is busy and the "destination" git repo is quiet?
We do not use symlinks in our working-tree or in our .git directory (unless
git is using symlinks on its own behind-the-scenes that I am not aware of).
This would make it very easy for us to refresh our "beta" livebox to emulate
the current "gold" livebox using a single rsync instead of a combination of
rsync and git-clone/pull due to the pieces that git does not replicate (ie,
hooks) and the non-git components of our git based change control menu
system (which is written in bash scripts on linux).
Thanks!
v/r,
Neal
next reply other threads:[~2011-03-08 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 21:25 Neal Kreitzinger [this message]
2011-03-08 21:39 ` rsync busy non-bare git repo 'source' to quiet Jeff King
2011-03-08 22:20 ` Neal Kreitzinger
2011-03-08 22:38 ` Jeff King
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='il66rd$46u$1@dough.gmane.org' \
--to=neal@rsss.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).