git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] Introduce git-mirror, a tool for exactly mirroring another repository.
Date: Tue, 31 Oct 2006 09:55:55 -0500	[thread overview]
Message-ID: <20061031145554.GA23007@spearce.org> (raw)
In-Reply-To: <20061031174225.3c7c1e77.vsu@altlinux.ru>

Sergey Vlasov <vsu@altlinux.ru> wrote:
> On Mon, 25 Sep 2006 00:46:41 -0400 Shawn Pearce 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.
> >   4) Automatically repack and prune the mirror when necessary.
> >
> > and since git-fetch doesn't do 2, 3, and 4 here's a tool that does.
> 
> Is this patch forgotten, abandoned or what?

Its waiting around for someone to clean it up.  :-)

Junio didn't accept it as there were a number of issues that he
identified in the patch.  I still have them in my inbox but have
not had time to go back and fix them.  Since I haven't actually had
a real need for git-mirror it has been low on my priority list of
"git things to do".

Your message pointed out a number of issues with the current version
that would be worth fixing before accepting it into git.git.  I agree
with many of them, especially about the direct ref manipulation.
git-mirror was written before the Linus packed ref stuff came
along, so git-update-ref didn't have a -d option at the time...
otherwise I would have used it.

-- 

  reply	other threads:[~2006-10-31 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25  4:46 [PATCH] Introduce git-mirror, a tool for exactly mirroring another repository Shawn Pearce
2006-09-26  4:45 ` Junio C Hamano
2006-09-26 21:57   ` Shawn Pearce
2006-10-31 14:42 ` Sergey Vlasov
2006-10-31 14:55   ` Shawn Pearce [this message]
2006-11-01  0:32   ` Junio C Hamano
2006-11-01  1:08     ` Jakub Narebski
2006-11-01 12:18       ` Sergey Vlasov
2006-11-01 12:23         ` Jakub Narebski
2006-11-01 16:15         ` 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=20061031145554.GA23007@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    --cc=vsu@altlinux.ru \
    /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).