From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: cg-clone produces "___" file and no working tree
Date: Thu, 20 Apr 2006 22:35:33 +0200 [thread overview]
Message-ID: <20060420203533.GG27689@pasky.or.cz> (raw)
In-Reply-To: <7vk69kxabp.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Thu, Apr 20, 2006 at 10:26:34PM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> Petr Baudis <pasky@suse.cz> writes:
>
> > Duh, but shouldn't git-init-db create .git/info at any rate, even when
> > no templates are installed?
>
> I do not think so. We tend to lazily create necessary
> directories under .git/ these days, and absolute minimum git
> should not need an empty .git/info directory.
>
> If there is something that creates files in .git/info without
> making sure that leading path exists, we should fix it (maybe
> update-server-info forgets it? I haven't checked).
Aww. cg-clone assumed that .git/info is canonical part of git repository
now and git-init-db will always creat eit, but now it seems to be the
case only for .git/objects/info.
I've fixed cg-clone. Thanks for the info.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time. I think
I have forgotten this before.
next prev parent reply other threads:[~2006-04-20 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 5:36 cg-clone produces "___" file and no working tree Zack Brown
2006-04-19 6:53 ` Junio C Hamano
2006-04-19 14:16 ` Zack Brown
2006-04-19 9:49 ` Petr Baudis
2006-04-19 14:21 ` Zack Brown
2006-04-19 14:48 ` Petr Baudis
2006-04-20 16:49 ` Zack Brown
2006-04-20 17:36 ` Junio C Hamano
2006-04-20 20:08 ` Zack Brown
2006-04-20 20:17 ` Junio C Hamano
2006-04-20 20:19 ` Petr Baudis
2006-04-20 20:26 ` Junio C Hamano
2006-04-20 20:35 ` Petr Baudis [this message]
2006-04-20 20:23 ` Junio C Hamano
2006-04-20 21:34 ` Zack Brown
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=20060420203533.GG27689@pasky.or.cz \
--to=pasky@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.