git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Wink Saville <wink@saville.com>
Cc: git@vger.kernel.org
Subject: Re: How-to setup an empty remote repository?
Date: Tue, 4 Sep 2007 21:47:49 +0200	[thread overview]
Message-ID: <20070904194749.GB3786@efreet.light.src> (raw)
In-Reply-To: <d4cf37a60708251400t17b0a097t91f77cbb4e996810@mail.gmail.com>

[-- 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 --]

      parent reply	other threads:[~2007-09-04 19:48 UTC|newest]

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

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=20070904194749.GB3786@efreet.light.src \
    --to=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=wink@saville.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.
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).