From: Donnie Berkholz <spyderous@gentoo.org>
To: Yann Dirson <ydirson@altern.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: irc usage..
Date: Sat, 20 May 2006 15:18:10 -0700 [thread overview]
Message-ID: <446F95A2.6040909@gentoo.org> (raw)
In-Reply-To: <20060520203911.GI6535@nowhere.earth>
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
Yann Dirson wrote:
> On Sat, May 20, 2006 at 10:26:22AM -0700, Linus Torvalds wrote:
>> I'm reading the irc logs, and seeing that people have problems, but (a) it
>> was while I was asleep and (b) irc use doesn't encourage people to
>> actually explain what the problems _are_, so I have no clue.
>>
>> So now I know that "spyderous" has problems importing some 1GB gentoo CVS
>> archive, but that's pretty much it. Grr.
Hi all,
I just subscribed and this post is the only one I've got from the
thread, so I'm responding to it instead of the original. Gentoo's an
IRC-based community, so I tend to try IRC first for any problems I have
and fall back to the list later if I can't get things figured out.
Here's a rough summary:
Our main repo is actually a bit over 2G (2103621223) now that I check,
but it's not very complex. There's actually just one branch, and I don't
think anyone would care if we lost the history from it because it's a
release branch from a few years ago.
Somebody else tried importing it with git-cvsimport, but he said he hit
some kind of problem and recalled that it was a cvsps segfault. Sounds
about right, since I've never gotten cvsps to run successfully on the
whole repo either.
I tried with parsecvs, but it runs into OOM even on a machine with 4G
RAM after reading in all the ,v files, presumably while it's building
some huge tree of changesets in memory. Keith Packard's suggested that
there are ways to reduce parsecvs's memory use, because it retains the
full tree in memory for each revision rather than just the files that
actually changed. But my C skills are pretty weak; I'm an OK reader but
not much of a writer yet.
Thanks,
Donnie
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-05-20 22:18 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 17:26 irc usage Linus Torvalds
2006-05-20 17:50 ` Junio C Hamano
2006-05-20 18:52 ` Jakub Narebski
2006-05-20 20:39 ` Yann Dirson
2006-05-20 22:18 ` Donnie Berkholz [this message]
2006-05-20 22:45 ` Linus Torvalds
2006-05-20 23:12 ` Donnie Berkholz
2006-05-21 19:24 ` Linus Torvalds
2006-05-22 3:59 ` Linus Torvalds
2006-05-22 4:19 ` Donnie Berkholz
2006-05-22 4:50 ` Linus Torvalds
2006-05-22 5:04 ` Martin Langhoff
2006-05-22 5:21 ` Donnie Berkholz
2006-05-22 7:42 ` Martin Langhoff
2006-05-22 9:13 ` Linus Torvalds
2006-05-22 12:54 ` Martin Langhoff
2006-05-22 17:27 ` Linus Torvalds
2006-05-22 17:51 ` Jakub Narebski
2006-05-22 18:03 ` Linus Torvalds
2006-05-22 19:03 ` Matthias Lederhofer
2006-05-22 19:09 ` Junio C Hamano
2006-05-23 20:19 ` Jakub Narebski
2006-05-22 19:46 ` Martin Langhoff
2006-05-22 19:09 ` Donnie Berkholz
2006-05-22 19:38 ` Linus Torvalds
2006-05-22 19:49 ` Donnie Berkholz
2006-05-22 20:20 ` Linus Torvalds
2006-05-22 21:48 ` Donnie Berkholz
2006-05-29 21:54 ` Donnie Berkholz
2006-05-29 22:21 ` Martin Langhoff
2006-05-29 22:32 ` Donnie Berkholz
2006-05-30 0:19 ` Martin Langhoff
2006-05-30 5:31 ` Donnie Berkholz
2006-05-30 6:01 ` Martin Langhoff
2006-05-30 0:43 ` Linus Torvalds
2006-05-30 22:31 ` Martin Langhoff
2006-05-30 23:07 ` Linus Torvalds
2006-05-31 1:04 ` Martin Langhoff
2006-05-31 2:49 ` Donnie Berkholz
2006-05-31 6:05 ` Martin Langhoff
2006-05-31 13:54 ` Alec Warner
2006-05-31 22:03 ` Martin Langhoff
2006-06-01 1:42 ` Alec Warner
2006-06-01 7:47 ` Martin Langhoff
2006-06-05 0:33 ` Alec Warner
2006-06-05 2:06 ` Martin Langhoff
2006-06-05 2:36 ` Alec Warner
2006-06-05 3:49 ` Martin Langhoff
2006-06-05 16:07 ` Sean
2006-06-05 16:07 ` Sean
2006-05-22 19:41 ` Martin Langhoff
2006-05-22 20:11 ` Linus Torvalds
2006-05-22 20:33 ` Linus Torvalds
2006-05-22 21:41 ` Matthias Urlichs
2006-05-22 22:18 ` Linus Torvalds
2006-05-22 23:23 ` Martin Langhoff
2006-05-22 23:29 ` Martin Langhoff
2006-05-22 23:33 ` Linus Torvalds
2006-05-22 22:39 ` Junio C Hamano
2006-05-22 23:15 ` Martin Langhoff
2006-05-23 6:52 ` Jeff King
2006-05-23 6:58 ` Jeff King
2006-05-23 7:01 ` [PATCH 1/2] cvsimport: use git-update-index --index-info Jeff King
2006-05-23 7:00 ` [PATCH 2/2] cvsimport: cleanup commit function Jeff King
[not found] ` <7v4pzh6wtr.fsf@assigned-by-dhcp.cox.net>
2006-05-23 7:13 ` Jeff King
2006-05-23 7:27 ` [PATCH 1/2] cvsimport: use git-update-index --index-info Jeff King
2006-05-23 8:13 ` [PATCH 2/2] cvsimport: cleanup commit function Martin Langhoff
2006-05-23 8:24 ` Junio C Hamano
2006-05-23 20:32 ` Martin Langhoff
2006-05-23 16:50 ` Linus Torvalds
2006-05-23 19:36 ` Linus Torvalds
2006-05-23 20:25 ` Junio C Hamano
2006-05-23 20:29 ` Martin Langhoff
2006-05-23 21:10 ` Jeff King
2006-05-23 21:13 ` Martin Langhoff
2006-05-23 17:47 ` Morten Welinder
2006-05-23 20:59 ` Jeff King
2006-05-23 23:41 ` Junio C Hamano
2006-05-24 9:52 ` Jeff King
2006-05-22 20:16 ` irc usage Donnie Berkholz
2006-05-21 9:46 ` Thomas Glanzmann
2006-05-21 1:14 ` Donnie Berkholz
2006-05-22 1:45 ` Linus Torvalds
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=446F95A2.6040909@gentoo.org \
--to=spyderous@gentoo.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=ydirson@altern.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 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.