From: Linus Torvalds <torvalds@osdl.org>
To: Franck <vagabon.xyz@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [QUESTION] Access to a huge GIT repository.
Date: Thu, 17 Nov 2005 08:23:07 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0511170817480.13959@g5.osdl.org> (raw)
In-Reply-To: <cda58cb80511170236p4a7e2baay@mail.gmail.com>
On Thu, 17 Nov 2005, Franck wrote:
>
> Sorry, I forget to tell that I have already tried what you suggested
> at first (except that I did not do a 'git repack -a -d') but it didn't
> work out (and that the reason why I tried the "kill father object"
> thing).
If that didn't work, then you can't kill the father object: it will not
only just get rid of one single object, but it will make fsck unhappy that
your tree is incomplete.
What you probably _can_ do is to find whatever top-most commit you want
(say, the v2.6.0 commit), and use grafting to make that have no parents.
Then you can do git-prune to get rid of everything under it.
> Since I forgot the repack thing, I retried again, and it did
> last more than 4 hours to cpmplete all git commands.
Sounds like the original archive was fully unpacked. That really does get
very very slow after a while.
> After that I run
> gitk --all to check that all old branch's objects have been removed
> but I can see all of them.
Note that if the branches are still there, git prune won't do anything to
them (and git repack will pack them all). You need to remove the branches
_first_, so that git repack and prune sees that their objects aren't
needed.
But yes, if the tree is actually based on some full CVS history and really
goes back all the way to 1995, then you can't prune it (since all branches
are actually part of the history from the very top), and you'd need to
graft away part of it like above.
Linus
next prev parent reply other threads:[~2005-11-17 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 12:24 [QUESTION] Access to a huge GIT repository Franck
2005-11-16 16:46 ` Linus Torvalds
2005-11-17 10:36 ` Franck
2005-11-17 16:23 ` Linus Torvalds [this message]
2005-11-17 21:47 ` Franck
2005-11-17 22:44 ` Linus Torvalds
2005-11-19 12:23 ` Franck
2005-11-19 12:45 ` Lukas Sandström
2005-11-19 20:42 ` Junio C Hamano
2005-11-19 17:56 ` Linus Torvalds
2005-11-19 19:52 ` Junio C Hamano
2005-11-21 20:11 ` Franck
2005-11-21 20:45 ` Junio C Hamano
2005-11-22 9:22 ` Franck
2005-11-22 9:50 ` Junio C Hamano
2005-11-22 10:40 ` Franck
2005-11-22 17:06 ` Junio C Hamano
2005-11-22 19:10 ` Franck
2005-11-16 18:24 ` Junio C Hamano
2005-11-16 20:01 ` Martin Langhoff
2005-11-16 20:10 ` Linus Torvalds
2005-11-16 20:35 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0511170817480.13959@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=vagabon.xyz@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).