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@xxxxxxxxxxxxxxxxx ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.
