git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Wink Saville" <wink@saville.com>
To: git@vger.kernel.org
Subject: How-to setup an empty remote repository?
Date: Sat, 25 Aug 2007 14:00:33 -0700	[thread overview]
Message-ID: <d4cf37a60708251400t17b0a097t91f77cbb4e996810@mail.gmail.com> (raw)

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

             reply	other threads:[~2007-08-25 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-25 21:00 Wink Saville [this message]
2007-08-25 22:06 ` How-to setup an empty remote repository? Petr Baudis
2007-08-25 22:45   ` Wink Saville
2007-09-04 19:47 ` Jan Hudec

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=d4cf37a60708251400t17b0a097t91f77cbb4e996810@mail.gmail.com \
    --to=wink@saville.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).