From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: [QUESTION] about .git/info/grafts file
Date: Thu, 19 Jan 2006 14:44:15 +0100 [thread overview]
Message-ID: <43CF97AF.9060300@op5.se> (raw)
In-Reply-To: <cda58cb80601190531q238a8f40r@mail.gmail.com>
Franck wrote:
> 2006/1/19, Andreas Ericsson <ae@op5.se>:
>>
>>I'm a bit curious about how this was done for the public kernel repo.
>>I'd like to import glibc to git, but keeping history since 1972 seems a
>>bloody waste, really.
>>
>
>
> That's exactly my point. Futhermore make your downloaders import that
> useless history spread this waste.
>
> I guess kernel repo will encounter this problem in short term. It's
> being bigger and bigger and developpers may be borred to deal with so
> many useless objects.
Ach, no. The current kernel repo only has history since April 17 (around
155 MB of objects, with less than optimal packing), when it started
using git for versioning. The kernel repo also sees a lot of very rapid
development.
The full kernel tree, with history since 1991 or some such, is about 3.2
GB. It was for this reason that the early history was dropped. I don't
think another drop will be necessary any time soon, since incremental
updates are fairly cheap over git and git+ssh. Only gitk suffers, but
that's just for a short while.
> But I'm not saying that it's bad thing to keep
> that history. It just would be nice to allow developpers that don't
> care about old history to get rid of it.
>
You could ofcourse create a new repository with the files from the
version you want, but then you'd have a hard time merging the two repos
if you ever want to import the old history.
Linus; Is this what you did with the public kernel repo?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-01-19 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cda58cb80601170928r252a6e34y@mail.gmail.com>
2006-01-17 17:32 ` [QUESTION] about .git/info/grafts file Franck
2006-01-18 17:47 ` Franck
2006-01-19 0:40 ` Junio C Hamano
2006-01-19 10:51 ` Franck
2006-01-19 13:09 ` Petr Baudis
2006-01-19 16:58 ` Linus Torvalds
2006-01-19 17:30 ` Petr Baudis
2006-01-19 17:33 ` Franck
2006-01-19 17:49 ` Linus Torvalds
2006-01-19 18:24 ` Junio C Hamano
2006-01-19 18:24 ` Junio C Hamano
2006-01-20 13:43 ` Franck
2006-01-19 11:10 ` Andreas Ericsson
2006-01-19 13:05 ` Petr Baudis
2006-01-19 13:31 ` Franck
2006-01-19 13:44 ` Andreas Ericsson [this message]
2006-01-19 17:45 ` Petr Baudis
2006-01-20 20:48 ` Ryan Anderson
2006-01-20 1:14 ` Junio C Hamano
2006-01-20 10:07 ` Franck
2006-01-20 17:59 ` 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=43CF97AF.9060300@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).