"J. Bruce Fields" [off-list ref] writes:
Hm. We tell people to set up public repo's by doing something like:
git clone --bare ~/proj proj.git
touch proj.git/git-daemon-export-ok
scp -r proj.git example.com:
Is that going to hit the same problem if the public server has an older
git version?
It will, but I think you should teach people --mirror pushing these
days, which was specifically invented for priming the public
repository.
That way, the administrator at example.com, as long as he initializes an
empty repository with suitable daemon-export-ok and necessary hooks
(which can be automated via templates), does not even have to allow you
a full ssh access.
On Mon, Dec 17, 2007 at 02:55:15PM -0800, Junio C Hamano wrote:
"J. Bruce Fields" [off-list ref] writes:
quoted
Hm. We tell people to set up public repo's by doing something like:
git clone --bare ~/proj proj.git
touch proj.git/git-daemon-export-ok
scp -r proj.git example.com:
Is that going to hit the same problem if the public server has an older
git version?
It will, but I think you should teach people --mirror pushing these
days, which was specifically invented for priming the public
repository.
That way, the administrator at example.com, as long as he initializes an
empty repository with suitable daemon-export-ok and necessary hooks
(which can be automated via templates), does not even have to allow you
a full ssh access.
So the basic instructions would be something like this?:
ssh example.com "git init --bare myproj.git"
# (or ask your admin to do the previous step)
git add remote example example.com:myproj.git
git push --mirror example
OK, that's neat, thanks.
On the backwards-compatibility issue, though: this won't help the large
number of people who learned to just clone a bare repo and copy it
around, since they aren't of their own initiative going to seek out new
ways of doing things that they think they already know how to do.
--b.