All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Graeme Geldenhuys <graemeg@gmail.com>, git@vger.kernel.org
Subject: Re: Correct way of making existing remote repository "bare"
Date: Wed, 15 Jul 2009 16:21:49 +0200	[thread overview]
Message-ID: <4A5DE5FD.80304@dirk.my1.cc> (raw)
In-Reply-To: <alpine.DEB.1.00.0907151607050.4410@intel-tinevez-2-302>

Am 15.07.2009 16:08 schrieb Johannes Schindelin:
> 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

  reply	other threads:[~2009-07-15 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 12:20 Correct way of making existing remote repository "bare" Graeme Geldenhuys
2009-07-15 14:08 ` Johannes Schindelin
2009-07-15 14:21   ` Dirk Süsserott [this message]
2009-07-15 14:44   ` Graeme Geldenhuys
2009-07-16  7:59   ` Eric Raible
2009-07-15 14:12 ` Dirk Süsserott
2009-07-15 19:39   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5DE5FD.80304@dirk.my1.cc \
    --to=newsletter@dirk.my1.cc \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=graemeg@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.