Re: Possible to make a totally empty repository for remote access?

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 13, 2007, 22:18 UTC
Message-ID: <7vtzs8lzgk.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <54C69B03-C589-480E-80D3-75166DBF2D29@wincent.com>

Wincent Colaiuta <win@wincent.com> writes:

Show 5 quoted lines

> I understand that Git is a *content* manager and a totally empty
> repository has no content, and therefore no tree object which the
> HEAD can point to. But the trouble with adding content the way I
> describe above, is that my public repository is no longer bare; it
> now has a working copy, which I didn't really want.

You prepared an empty bare repository for publishing, and that is very good.

The next step is that you prepare your contents elsewhere. That would be your private working place, i.e. the place you would normally work in). You push from your private working place into that publishing repository. Your working place is where the very initial commit should come from, since you are the one who is starting the project.

Note that the private working place does not have to be a clone of the empty one. That actually is backwards. Your work started from your private working place to the publishing one.

You could even clone your private repository to publishing one to make it clear who is the master and who is the copy if you wanted to, but because you already have the bare repository for publishing, just pushing into it is all that is needed.