Am 15.07.2009 14:20 schrieb Graeme Geldenhuys:
Hi,
Yesterday I initialized a new repository on our server. I did some
coding locally, added the remote server (git remote add ....) and then
pushed my changes to the remote server.
But I noticed that my remote server is not a "bare" repository and git
complains when I push to it again. What is the correct way to make an
existing remote repository bare?
This is what I did and it worked, but not sure if this is the correct
way of doing it.
Steps I done:
* ssh to remote server
* git clone --bare -l <path_to_repos> <new_dir>
* renamed old repository directory
* renamed new repository dir to what old repository used to be.
Like I said, this did the tick, but is this the correct way of doing it?
Regards,
- Graeme -
Sounds like that's the correct way. I sometimes faced the same problem
and was lazy:
$ ssh to the remote && cd repo
$ rm everything except for the .git directory (make sure everything is
committed before doing this)
$ mv .git/* . && rmdir .git # i.e.move the .git contents one level up
$ edit config
change 'core.bare=false' to 'core.bare=true' (or add a similar line)
done.
I think what you did is 'porcellain' while my solution is 'plumbing'.
Any complaints?
Dirk
--
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