From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Dan Farina <drfarina@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: backup or mirror a repository
Date: Tue, 30 Oct 2007 00:33:05 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710300030530.4362@racer.site> (raw)
In-Reply-To: <20071018053226.GA20588@dpotapov.dyndns.org>
Hi,
On Thu, 18 Oct 2007, Dmitry Potapov wrote:
> On Thu, Sep 27, 2007 at 11:27:06PM -0700, Junio C Hamano wrote:
> > The "git remote add --mirror" setup is about setting up the
> > local repository _AS_ the backup of the remote. In other words,
> > the contents come from the remote by fetching from it and safely
> > kept away from disaster on the local side. And for that,
> > "remote prune" is a perfect thing to do.
>
> I have tried to do that but I am getting a warning:
> $ git remote prune origin
> Warning: unrecognized mapping in remotes.origin.fetch: +refs/*:refs/*
> and no branch is removed.
>
> I suspect that the change that introduced --mirror option for the 'add'
> command did not adjust the prune procedure to handle the new situation
> properly. Or is just me doing something wrong?
No, you're right. I did not anticipate git-remote to be written the way
it is. After fiddling with it for several hours, I am giving up for now.
IMHO the script is too married to the idea that the remote branches live
in refs/remotes/<remote>/*. Probably it would be very easy by now to
implement it as a builtin, using remote.[ch].
Ciao,
Dscho
prev parent reply other threads:[~2007-10-30 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 19:35 backup or mirror a repository Dan Farina
2007-09-27 21:56 ` Johannes Schindelin
2007-09-28 0:51 ` Dan Farina
2007-09-28 1:56 ` Johannes Schindelin
2007-09-28 2:37 ` Dan Farina
2007-09-28 6:27 ` Junio C Hamano
2007-09-28 7:20 ` Dan Farina
2007-10-18 5:32 ` Dmitry Potapov
2007-10-30 0:33 ` Johannes Schindelin [this message]
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=Pine.LNX.4.64.0710300030530.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dpotapov@gmail.com \
--cc=drfarina@gmail.com \
--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).