From: Andy Whitcroft <apw@shadowen.org>
To: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: git push mirror mode V4 (replacement stack)
Date: Mon, 12 Nov 2007 11:00:16 +0000 [thread overview]
Message-ID: <20071112110016.GG301@shadowen.org> (raw)
In-Reply-To: <20071109233041.GC301@shadowen.org>
On Fri, Nov 09, 2007 at 11:30:41PM +0000, Andy Whitcroft wrote:
> Following this mail is a complete replacement git push mirror mode
> stack (V4). It folds down all the various patches into a logical
> sequence (thanks Dscho). This stack passes the entire test suite,
> and I have been using the same code for real work here.
Ok, I have spotted one oddity with this feature. The symbolic refs are
getting converted to real refs in the mirror. Generally speaking this
is the <remote>/HEAD refs but I guess it may be possible to have others.
I have had a looked about and I am actually confused as to whether we
maintain remote symbolic refs at all? Cirtainly git-clone.sh seems to
do some hoop jumping, comparing the sha1's of all of the fetched branches
and replacing the HEAD reference with a symbolic reference should it find
a match.
I am unsure if this a huge problem or not. Its not preventing me using
it as an effective mirror, but if we assume one is making the mirror as
a backup, then there would be slightly more than an rsync to convert the
the repo back into your original, though I guess there already is as you
would want to insert your config into the remote also.
Perhaps someone with a better understanding could point me to where we
we maintain these refs, if we indeed do?
-apw
next prev parent reply other threads:[~2007-11-12 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 23:30 git push mirror mode V4 (replacement stack) Andy Whitcroft
2007-11-09 23:32 ` [PATCH 1/4] Teach send-pack a mirror mode Andy Whitcroft
2007-11-09 23:32 ` [PATCH 2/4] git-push: plumb in --mirror mode Andy Whitcroft
2007-11-09 23:32 ` [PATCH 3/4] Add tests for git push'es mirror mode Andy Whitcroft
2007-11-09 23:32 ` [PATCH 4/4] git-push: add documentation for the newly added --mirror mode Andy Whitcroft
2007-11-12 11:00 ` Andy Whitcroft [this message]
2007-11-12 21:35 ` git push mirror mode V4 (replacement stack) Junio C Hamano
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=20071112110016.GG301@shadowen.org \
--to=apw@shadowen.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).