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

Re: Correct way of making existing remote repository "bare"

From
DSDirk Süsserott <newsletter@dirk.my1.cc>
Date
Jul 15, 2009, 14:21 UTC
Message-ID
<4A5DE5FD.80304@dirk.my1.cc>
In-Reply-To
<alpine.DEB.1.00.0907151607050.4410@intel-tinevez-2-302>
Am 15.07.2009 16:08 schrieb Johannes Schindelin:
Show 23 quoted lines
> Hi,
> 
> On Wed, 15 Jul 2009, Graeme Geldenhuys wrote:
> 
>> 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?
> 
> That's the easiest.  However, I regularly avoid those steps by doing
> 
> 	mv bla/.git bla.git
> 	git --git-dir=bla.git config core.bare true
> 	rm -rf bla
> 
> This requires a bit more familiarity with the Git internals than your 
> solution, though (although it makes sure that the config is unchanged, as 
> well as possibly installed hooks).
> 
Dscho, you boiled down my solution to real git commands. Great. -- Dirk
Previous: Johannes SchindelinNext: Graeme Geldenhuys
Message 3 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.