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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
