git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Correct way of making existing remote repository "bare"

From
Graeme Geldenhuys <graemeg@gmail.com>
Date
Jul 15, 2009, 12:20 UTC
Message-ID
<h3khis$3tq$1@ger.gmane.org>
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 -
-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
Next: Johannes Schindelin
Message 1 of 7 in “Correct way of making existing remote repository "bare"”
  1. Graeme GeldenhuysJul 15, 2009
  2. Johannes SchindelinJul 15, 2009
  3. Dirk SüsserottJul 15, 2009
  4. Graeme GeldenhuysJul 15, 2009
  5. Eric RaibleJul 16, 2009
  6. Dirk SüsserottJul 15, 2009
  7. Junio C HamanoJul 15, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.