Git development
 help / color / mirror / Atom feed
From: barkalow@iabervon.org
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Use the template mechanism to set up refs/ hierarchy as well.
Date: Thu, 4 Aug 2005 18:08:47 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0508041804120.23721@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0508042215430.24657@wgmdd8.biozentrum.uni-wuerzburg.de>

On Thu, 4 Aug 2005, Johannes Schindelin wrote:

> > * 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.

Are .git/refs/heads and .git/refs/tags still needed? I seem to recall a 
patch to create subdirectories of .git/refs on demand (needed for 
tags/v99/1). I'd say just .git/objects/(everything), .git/refs, and 
.git/info.

(Plus template, if available, of course)

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2005-08-04 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  6:28 [PATCH] Use the template mechanism to set up refs/ hierarchy as well Junio C Hamano
2005-08-04 18:41 ` Johannes Schindelin
2005-08-04 19:59   ` Junio C Hamano
2005-08-04 20:19     ` Johannes Schindelin
2005-08-04 20:50       ` Junio C Hamano
2005-08-04 21:13         ` Johannes Schindelin
2005-08-04 21:35           ` Junio C Hamano
2005-08-05  0:35             ` Johannes Schindelin
2005-08-04 22:08       ` barkalow [this message]
2005-08-05  0:20         ` Junio C Hamano

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

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

  git send-email \
    --in-reply-to=Pine.LNX.4.62.0508041804120.23721@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox