From: Chris Friesen <chris.friesen@genband.com>
To: git@vger.kernel.org
Subject: any way to "re-sync" a bare repository against another bare repository?
Date: Thu, 22 Sep 2011 11:22:37 -0600 [thread overview]
Message-ID: <4E7B6EDD.1040106@genband.com> (raw)
Suppose I have a parent bare repository. I do a "git clone --bare" to
create a child repository, and then clone the child to create a
grandchild repository.
If changes get pushed into the parent repository, is there any way to
cause the child to be updated?
Just a "git fetch <parent>" doesn't seem to help. If I set up parent as
a remote branch I can fetch it, but then it shows all the branches as
"parent/<branch>" rather than updating the child.
I just tried a "git clone --mirror" to create the child and it seems to
allow me to pick up changes in the parent via "git fetch". Is that the
proper way to handle this?
Thanks,
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next reply other threads:[~2011-09-22 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 17:22 Chris Friesen [this message]
2011-09-22 18:50 ` any way to "re-sync" a bare repository against another bare repository? Michael Witten
2011-09-22 19:23 ` Chris Friesen
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=4E7B6EDD.1040106@genband.com \
--to=chris.friesen@genband.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).