From: Junio C Hamano <junkio@cox.net>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: git@vger.kernel.org
Subject: Re: GIT_OBJECT_DIRECTORY
Date: Tue, 18 Apr 2006 11:20:58 -0700 [thread overview]
Message-ID: <7vfykag2yd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060418175853.GA25688@wohnheim.fh-wedel.de> (Jörn Engel's message of "Tue, 18 Apr 2006 19:58:53 +0200")
Jörn Engel <joern@wohnheim.fh-wedel.de> writes:
> Well, .git/objects for your kernel still consumes 121M. It's not
> gigabytes but I still wouldn't want too many copies of that lying
> around.
That is what "git clone -l -s" is for.
The alternates pointer mechanism used with the above largely
makes GIT_OBJECT_DIRECTORY unnecessary for end users these days.
It is a fine mechanism as an implementation detail of the
lowlevel and Porcelains, and that is the reason the
documentation still mentions the environment.
next prev parent reply other threads:[~2006-04-18 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 13:38 GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-18 15:25 ` GIT_OBJECT_DIRECTORY Linus Torvalds
2006-04-18 17:58 ` GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-18 18:07 ` GIT_OBJECT_DIRECTORY Sam Ravnborg
2006-04-18 18:08 ` GIT_OBJECT_DIRECTORY Linus Torvalds
2006-04-18 18:26 ` GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-18 18:47 ` GIT_OBJECT_DIRECTORY Linus Torvalds
2006-04-18 18:58 ` GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-19 4:51 ` GIT_OBJECT_DIRECTORY H. Peter Anvin
2006-04-19 5:00 ` GIT_OBJECT_DIRECTORY Junio C Hamano
2006-04-18 18:20 ` Junio C Hamano [this message]
2006-04-18 18:45 ` GIT_OBJECT_DIRECTORY Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 14:10 GIT_OBJECT_DIRECTORY linux
2006-04-18 14:16 ` GIT_OBJECT_DIRECTORY Jörn Engel
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=7vfykag2yd.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=joern@wohnheim.fh-wedel.de \
/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