How-to setup an empty remote repository?

How-to setup an empty remote repository?

[Wink Saville]

Hello,

I thought I'd try to setup a shared "empty" remote repository and then
clone it and then push the initial commit from another maching.
This failed as shown below:

 $ cd ~/git-repos
 $ mkdir test.git
 $ cd test.git
 $ git --bare init --shared
 Initialized empty shared Git repository in /home/wink/git-repos/test.git/
 $ git-daemon --reuseaddr --verbose --base-path=/home/wink/git-repos \
    --export-all --enable=receive-pack

On my other machine:

$ git clone git://192.168.0.8/test.git
Initialized empty Git repository in /home/wink/prgs/test/.git/
fatal: no matching remote head
fetch-pack from 'git://192.168.0.8/test.git' failed.
$

And the remote machine responded:

[27299] Connection from 192.168.0.133:56710
[27299] Extended attributes (18 bytes) exist <host=192.168.0.8>
[27299] Request upload-pack for '/test.git'
[27299] Disconnected

In the instructions I followed for setting up a remote repository,
http://www.kernel.org/pub/software/scm/git/docs/cvs-migration.html,
it uses an existing repository. So is it true you can't clone an
empty remote repository, or did I do something wrong?

I'm using :
$ git --version
git version 1.5.3.rc6.23.g0058

Note, my reason for using the shared remote repository is to make it
simple and easy to backup my repository on a second machine and
it seemed reasonable to try a an empty repository.

Cheers,

Wink Saville

Re: How-to setup an empty remote repository?

[Petr Baudis]

On Sat, Aug 25, 2007 at 11:00:33PM CEST, Wink Saville wrote:
> In the instructions I followed for setting up a remote repository,
> http://www.kernel.org/pub/software/scm/git/docs/cvs-migration.html,
> it uses an existing repository. So is it true you can't clone an
> empty remote repository, or did I do something wrong?

It is true that you can't clone it. "Cloning remote repository" means
just "get all the remote branches and set them up locally". In empty
repository there are no branches yet, so there's nothing to clone.

I guess this should be covered in the FAQ (if it isn't already), it is
one of the top questions repo.or.cz users have and I think I see it
frequently on IRC as well.

-- 
				Petr "Pasky" Baudis
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
		-- Samuel Beckett

Re: How-to setup an empty remote repository?

[Wink Saville]

On 8/25/07, Petr Baudis <pasky@suse.cz> wrote:
> On Sat, Aug 25, 2007 at 11:00:33PM CEST, Wink Saville wrote:
> > In the instructions I followed for setting up a remote repository,
> > http://www.kernel.org/pub/software/scm/git/docs/cvs-migration.html,
> > it uses an existing repository. So is it true you can't clone an
> > empty remote repository, or did I do something wrong?
>
> It is true that you can't clone it. "Cloning remote repository" means
> just "get all the remote branches and set them up locally". In empty
> repository there are no branches yet, so there's nothing to clone.
>
> I guess this should be covered in the FAQ (if it isn't already), it is
> one of the top questions repo.or.cz users have and I think I see it
> frequently on IRC as well.
>
> --

I didn't see it here, http://git.or.cz/gitwiki/GitFaq.

I would have expected it to setup an empty repository and then
populate it with 0 remote branches. Obviously, its a corner case
and maybe doesn't need addressing but if it is asked a lot then
maybe it should work that way.

Thanks,

Wink

Re: How-to setup an empty remote repository?

[Jan Hudec]

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Sat, Aug 25, 2007 at 14:00:33 -0700, Wink Saville wrote:
> Hello,
> 
> I thought I'd try to setup a shared "empty" remote repository and then
> clone it and then push the initial commit from another maching.
> This failed as shown below:
> 
>  $ cd ~/git-repos
>  $ mkdir test.git
>  $ cd test.git
>  $ git --bare init --shared
>  Initialized empty shared Git repository in /home/wink/git-repos/test.git/
>  $ git-daemon --reuseaddr --verbose --base-path=/home/wink/git-repos \
>     --export-all --enable=receive-pack
> 
> On my other machine:
> 
> $ git clone git://192.168.0.8/test.git
> Initialized empty Git repository in /home/wink/prgs/test/.git/
> fatal: no matching remote head
> fetch-pack from 'git://192.168.0.8/test.git' failed.
> $

Did it configure the repository though? Like setting the url and tracking
branches for origin? If it did, it actually did all you needed, so you can
count it as success (and the message should talk about having nothing to do
rather than failing).

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]