Talk:Creating Shared Git Repo

From LSDevLinux
Jump to: navigation, search

Setup

  1. I don't think the global config is necessary when creating a bare repo. After all, no commits are being made.
  2. Rahab's version of git doesn't seem to allow you to specify a directory name with init. You have to:
    mkdir PROJECTNAME.git; cd PROJECTNAME.git; git init --bare --shared=group
  3. I'd prefer us just not to offer http access, and since this may go away at some point in the future I think we shouldn't include this in our instructions. Http is useful only for people whose company firewall blocks outgoing git connections, and if we get a request from someone like that we can consider enabling it then.
  4. After cloning, origin will already be set up as a remote, so git push should be sufficient. At the most it should be git push origin master. Putting the whole ssh URL in the instructions seems offputting.

--Neil Mayhew 23:28, 18 November 2010 (UTC)

Actually, I've just realized we don't really offer http access: http://git.lsdev.sil.org/ takes you to the gitweb interface. Access is still possible using the right URL (ie http://linux.lsdev.sil.org/git/public/PROJECTNAME.git/) but this is an anomaly and I plan to take this away eventually.

So I'm taking out the http references altogether.

--Neil Mayhew 00:01, 19 November 2010 (UTC)

So you don't think we need the 'chmod +x hooks/post-update' step?

--Eberhard Beilharz 9:12, 19 November 2010 (UTC)

No, that hook is only for supporting "dumb transports" like http, and since we are not offering http access I've taken that out.

[hooks/post-update just runs git-update-server-info, for which the man page says, "Update auxiliary info file to help dumb servers". It doesn't do any harm, but it's not necessary either.]

--Neil Mayhew 17:08, 19 November 2010 (UTC)

However, there are other hooks we might want to enable. For example, in balsa-builder.git I have enabled hooks/post-receive, and added lines to config to send email when anything is pushed to the repo. We might want to do this for some of our other public repos, too.

--Neil Mayhew 17:16, 19 November 2010 (UTC)

Filling with content

Since the repo won't be empty for long, isn't it better to put up with the warning rather than put a junk file and commit into it?

--Neil Mayhew 23:29, 18 November 2010 (UTC)