From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: GIT_OBJECT_DIRECTORY
Date: Tue, 18 Apr 2006 19:58:53 +0200 [thread overview]
Message-ID: <20060418175853.GA25688@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0604180822470.3701@g5.osdl.org>
On Tue, 18 April 2006 08:25:47 -0700, Linus Torvalds wrote:
> On Tue, 18 Apr 2006, Jörn Engel wrote:
> >
> > $ git clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git foo
> > [ stored >200M of data under foo/.git/objects ]
> >
> > The above looks as if new objects are not stored under
> > /home/joern/.git, as specified by GIT_OBJECT_DIRECTORY.
>
> The "rsync" protocol really doesn't honor git rules. It's basically just a
> big recursive copy, and it will copy things from the place they were
> before.
>
> I suspect that if you had used a real git-aware protocol instead, you'd
> have been fine, ie
>
> git clone git://git.kernel.org/... foo/
Is it possible for non-owners of a kernel.org account to do this?
> would probably work. (I say "probably", because very few people likely use
> GIT_OBJECT_DIRECTORY, and it makes a lot less sense with pack-files than
> it did originally, so it's not getting any testing).
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. Right now, I already feel slightly motivated to move the
whole content-addressable idea into the kernel. It has disadvantages,
but the effect on disk- and pagecache-footprint for people like me
would come in handy.
Jörn
--
The cheapest, fastest and most reliable components of a computer
system are those that aren't there.
-- Gordon Bell, DEC labratories
next prev parent reply other threads:[~2006-04-18 17:59 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 ` Jörn Engel [this message]
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 ` GIT_OBJECT_DIRECTORY Junio C Hamano
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=20060418175853.GA25688@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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