From: A Large Angry SCM <gitzilla@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] [PATCH] git-mirror - exactly mirror another repository
Date: Thu, 26 Apr 2007 22:47:07 -0400 [thread overview]
Message-ID: <4631642B.2010501@gmail.com> (raw)
In-Reply-To: <20070427021505.1740.58136.stgit@rover>
Petr Baudis wrote:
> Sometimes its handy to be able to efficiently backup or mirror one
> Git repository to another Git repository by employing the native
> Git object transfer protocol. But when mirroring or backing up a
> repository you really want:
>
> 1) Every object in the source to go to the mirror.
> 2) Every ref in the source to go to the mirror.
> 3) Any ref removed from the source to be removed from the mirror.
>
> and since git-fetch doesn't do 2 and 3, here's a tool that does.
>
> This is based on Shawn Pearce's patch from 25 Sep 2006, updated to take
> Junio's and Sergey's review into account, to use few newer pieces of Git
> infrastructure and with few trivial tweaks. The repacking part was dropped
> since git-fetch does that on its own now.
>
> I actually still would kind of prefer this to be a git-fetch's feature but
> the general mood seems to be to have this as a separate command and I can't
> say I care at all.
>
It would be nice if this had an option to not mirror HEAD and another
option to map the refs from (/ref/[^/])/(.*) to /ref/\1/${repo_path}/\2.
next prev parent reply other threads:[~2007-04-27 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 2:15 [PATCH] [PATCH] git-mirror - exactly mirror another repository Petr Baudis
2007-04-27 2:17 ` Petr Baudis
2007-04-27 2:47 ` A Large Angry SCM [this message]
2007-04-27 4:38 ` Petr Baudis
2007-04-27 18:00 ` Petr Baudis
2007-04-27 8:56 ` Johannes Schindelin
2007-04-27 8:58 ` Andy Whitcroft
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=4631642B.2010501@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).