git - renaming already existing package

[Kacper Kornet]

On Fri, Oct 05, 2012 at 03:49:51PM +0200, Jakub Bogusz wrote:
> On Fri, Sep 28, 2012 at 05:46:52PM +0200, Kacper Kornet wrote:
> > On Mon, Sep 24, 2012 at 05:10:32PM +0300, Elan Ruusamäe wrote:
> > > On 10.09.2012 20:45, Jakub Bogusz wrote:
> > > >On Sat, Sep 08, 2012 at 10:08:36PM +0200, Jakub Bogusz wrote:
> > > >>>What is the procedure to rename already existing (also on ftp) package
> > > >>>after moving to git?

> > > >>>cvs2git howto says "ssh git at ... move ... ..." instead of rename -
> > > >>>is it appropriate for such case (would old package be accessible using
> > > >>>old name/auto tag?) - in cvs cp was invoked instead of mv.
> > > >>>Or should old repo be imported as new under new name?
> > > >OK, I've checked that "move" clones the repo in fact,
> > > >and writes ".gitolite.down" file (what does it do?).
> > > >Should I do something with the old package repo then? (trash?)
> > > i noticed too, that it clones to new repo and does nothing with old repo

> > > i.e the old repo seems to be
> > > 1) browseable from gitweb
> > > 2) cloneable from ssh+git url
> > > 3) cloneable from git url
> > > 4) fully available in github mirror

> > > so it's not working fully?

> > It works as intended. The old version is read only. And attempt to push
> > to it will result in printing the content of .gitolite.down file with
> > information that the package has been renamed.

> OK.

> Is there a way to just copy a repo (without setting the old one r/o)?

It can be done by creating a new repository and pushing to it. The only
thing which cannot be copied this way are auto- tags and RA- branches. 
But if there is a demand for full copy I can add such a functionality.
I just didn't expect that it would be needed.

-- 
  Kacper