On Mon, May 28, 2012 at 1:59 AM,
ffa <
ako...@mindboxstudios.com> wrote:
> git push --mirror does not work for me. I get two errors. One error is for
> branches "can not create new references".
Seeing the terminal output would help.
> The other is for tags which initially pushes successfully, but then
> failed with "failed to lock".
I've seen this message too, and I think it's caused by a) the tag
already exists or b) there are no branches pointing to the tag (making
the tag invisible to clients).
> If I grant all privileges to refs/*, it pushes, but when I clone, nothing
> shows. The GUI shows nothing under the branches section of the
> project. And, It doesn't seem to push the branches under refs/heads/.
Instead of using --mirror, push a single branch and see what happens.
git push ssh://user@host:29418/path/to/git mybranch:refs/heads/mybranch
(Or origin/mybranch:refs/heads/mybranch or whatever it is that you're pushing.)
Is the push reported as successful? Does it show up on the Branches
page? Is there a change in the refs in the underlying git on the
server (assuming you have server access)?
> Is everyone using repo to do stuff like this? Because, all of my
> searches seem to return discussions about using repo to mirror
> or initialize the mirror.
If you're dealing with multiple gits managed by Repo, it's natural to
use Repo (specifically the "forall" subcommand) to automate operations
for all gits. Apart from that, Repo has nothing to do with the pushes.
It's just a wrapper tool to ease the pain of dealing with hundreds of
gits.
--
Magnus Bäck
ba...@google.com