Re: committing to a checked out branch
From: Jeff Brown <hidden>
Date: 2016-06-15 22:46:47
On Mon, May 18, 2009 at 9:17 PM, Jay Soffian [off-list ref] wrote:
On Mon, May 18, 2009 at 8:33 PM, Jeff Brown [off-list ref] wrote:quoted
The workspace on my server is currently "checked out" so I get the big warning message every time I push to there. What is the best way to cleanup that working area so I can push to it without the large warning every time I commit. I know I can set a config variable to squelch the message but that isn't what I want to do. I want to make the workspace on the server _not_ be checked out. Thanks for the help.If you never want to checkout any branches in that repo on your server, then what you want is a bare repository. The easiest way to create it is as follows: $ git clone --bare /path/to/repo /path/to/repo.git Then you can remove /path/to/repo after verifying everything is sane. Note the ".git" extension is a convention denoting the repository is bare (vs "repo/.git", which implies a repository with a working copy). j.
Very good. That appears to have worked nicely. I appreciate the help. When I create a new repo on my server I have been creating an empty directory, then git init, then git add some file and commit. I expect that is the long/wrong way to initialize a repo, especially if I want it to be bare. What is the best approach to creating a cloneable bare repo? jb -- Jeff Brown SpringSource http://www.springsource.com/ Autism Strikes 1 in 166 Find The Cause ~ Find The Cure http://www.autismspeaks.org/