Difference between revisions of "Talk:Creating Shared Git Repo"

From LSDevLinux
Jump to: navigation, search
(Setup suggestions)
 
(Empty repo question)
Line 8: Line 8:
  
 
--[[User:Mayhewn|Neil Mayhew]] 23:28, 18 November 2010 (UTC)
 
--[[User:Mayhewn|Neil Mayhew]] 23:28, 18 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?
 +
 +
--[[User:Mayhewn|Neil Mayhew]] 23:29, 18 November 2010 (UTC)

Revision as of 17:29, 18 November 2010

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)


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)