From: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
To: devel@morey-chaisemartin.com
Cc: git@vger.kernel.org
Subject: Re: Newbie Query
Date: Tue, 20 Jan 2009 16:24:25 -0600 [thread overview]
Message-ID: <200901201624.30131.bss@iguanasuicide.net> (raw)
In-Reply-To: <49764647.1080606@morey-chaisemartin.com>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
On Tuesday 2009 January 20 15:46:47 Nicolas Morey-Chaisemartin wrote:
>Boyd Stephen Smith Jr. a écrit :
>> On Tuesday 2009 January 20 15:07:55 Nicolas Morey-Chaisemartin wrote:
>>> I did the rookie mistkae on the central server to create the main
>>> reposity in non-bare mode.
>>> Is there a cleaner way to convert a non-bare git repo into a bare repo
>>> than cloning it?
No.
>>> My repo have a lot of remote branch registered, and cloning them to a
>>> new bare repo mean I'll have to add all those remote branches again
>>> (except if there is another trick here I don't know about).
>>
>> Well, if you can make sure no one is pushing into the repo for a bit:
>> clone it and replace the original with a symlink to new, bare one. Your
>> clients will be able to use the same URL, so they should be happy. (I
>> haven't tried this, but it should work.)
>
>Well I know there are solutions to convert it to a bare repo.
>I was just wondering if there was a "clean" one which really converts
>the repo to a bare one and not create a copy which is bare.
The clone *is* a way to convert, with the added advantage of not trashing the
original during the conversion, by putting the results in a different
location. In fact, it's probably *cleaner* than any convert-in-place.
>I don't know how bare/non-bare is managed but I guess both types of repo
>are not differing by much, so it'd be great to have a function to
>convert from one to another.
I couldn't tell you all the differences, but I don't think there are many
either.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-20 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 19:19 Newbie Query Chris Willard
2009-01-20 20:00 ` Tomas Carnecky
2009-01-20 20:16 ` Sverre Rabbelier
2009-01-20 20:17 ` Reece Dunn
2009-01-20 21:07 ` Nicolas Morey-Chaisemartin
2009-01-20 21:34 ` Boyd Stephen Smith Jr.
2009-01-20 21:46 ` Nicolas Morey-Chaisemartin
2009-01-20 22:24 ` Boyd Stephen Smith Jr. [this message]
2009-01-20 23:51 ` Jeff King
2009-01-21 0:05 ` Johannes Schindelin
2009-01-21 14:31 ` Chris Willard
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=200901201624.30131.bss@iguanasuicide.net \
--to=bss@iguanasuicide.net \
--cc=devel@morey-chaisemartin.com \
--cc=git@vger.kernel.org \
/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.