Pushing to refs/for/branchname will create changes for each commit,
and this would of course be stupid, but if you instead push to
refs/heads/branchname you'll bypass the code review and push the
commits straight into the branch.
Now, a git is just files in a file system so you could use
rsync or similar, but I'd just push everything.
I've experienced out of memory problems when pushing a large repository
(like the Linux kernel) to the server, but that was over a year ago on
an underpowered virtual machine with an old Gerrit release. A workaround
then was to push a little bit a time instead of everything in one go.
--
Magnus B�ck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
> So you mean if i have a hundred of git projects, I would create them
> first by a hand-written script. And push them each by each?
Something like that. Of course, given a list of gits the creation and
push operations would be accomplished with a simple for loop in the
shell. If you have the gits listed in a Repo manifest you can even have
Repo do the looping for you -- have a look at the "repo forall" command.
You could rsync them, then re-run the 'init' command and tell it where
you rsync'ed the gits to.
Nasser
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
If you do this, you need to ensure you have granted yourself the
following permissions:
Push Branch +2 (or +3)
Forge Identity +2 (or +3)
I would just add these to -- All Projects -- for group Administrators
and reference refs/*. That way you can push to all of your projects
to setup the import, and then remove these two lines once done.