Re: What's cooking in git.git (Jan 2009, #07; Wed, 28)

From: Sverre Rabbelier <srabbelier@gmail.com>
Date: Jan 29, 2009, 11:27 UTC
Message-ID: <bd6139dc0901290327u572cc30ci9dc719c912fbf875@mail.gmail.com>
In-Reply-To: <20090129035138.GC11836@coredump.intra.peff.net>

On Thu, Jan 29, 2009 at 04:51, Jeff King <peff@peff.net> wrote:

Show 13 quoted lines

>  $ mkdir parent && (cd parent && git init)
>  Initialized empty Git repository in /home/peff/parent/.git/
>
>  $ git clone parent child
>  Initialized empty Git repository in /home/peff/child/.git/
>  warning: You appear to have cloned an empty repository.
>
> So far so good...
>
>  $ (cd parent && echo content >file && git add file && git commit -m one)
>  [normal commit output]
>  $ (cd child && git fetch)
>  [normal fetch output]

I thought instead we wanted to support the following workflow:

$ (cd child && echo content >file && git add file && git commit -m one) [normal commit output]

Which is what the testcase tests. E.g., we want to support cloning an empty repo so that the user can then _push_ to that repository to make it non-empty, no?

-- 
Cheers,

Sverre Rabbelier