Re: [PATCH] Use the template mechanism to set up refs/ hierarchy as well.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Aug 4, 2005, 20:19 UTC
Message-ID: <Pine.LNX.4.63.0508042215430.24657@wgmdd8.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vll3hxykj.fsf@assigned-by-dhcp.cox.net>

Hi,

On Thu, 4 Aug 2005, Junio C Hamano wrote:

Show 15 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>>> This may be controversial from the robustness standpoint, so I
>>> am placing it in the proposed update queue first.  Discussions
>>> on the list very welcomed.
>>
>> I'd vote against it: As of now, I can perfectly do
>>
>> export PATH=$PATH:/whereever/my/git/is
>> git-init-db
>>
>> which would not work with this patch.
>
> I take it to mean that you do not mind building but would want
> to try it out before installing.

I'd like to not being forced to install git. Scenario: I have an SSH account on a remote machine. I am not root there, but I'd like to synchronize my work with git. I can not install git.

> * Make git-init-db create an absolute minimum $GIT_DIR
>   structure itself, if the template directory is not available,
>   possibly with a warning.

This would be exactly what I'd like. Let git-init-db create .git/objects/[0-9a-f]{2}/, .git/refs/heads/, .git/refs/tags and .git/HEAD. Everything else is taken from the templates directory, if that exists. I would not warn if it does not.

Ciao, Dscho