From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31696 invoked by alias); 22 Aug 2013 21:10:50 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 31679 invoked by uid 89); 22 Aug 2013 21:10:50 -0000 X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 22 Aug 2013 21:10:49 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7MLAm3l005862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Aug 2013 17:10:48 -0400 Received: from barimba (ovpn-113-142.phx2.redhat.com [10.3.113.142]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r7MLAkRE022234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Aug 2013 17:10:47 -0400 From: Tom Tromey To: Mark Kettenis Cc: gdb@sourceware.org, binutils@sourceware.org Subject: Re: A Proposal to Move to Git References: <8738q4gj7a.fsf@fleche.redhat.com> <201308222010.r7MKAljG013904@glazunov.sibelius.xs4all.nl> Date: Thu, 22 Aug 2013 21:10:00 -0000 In-Reply-To: <201308222010.r7MKAljG013904@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Thu, 22 Aug 2013 22:10:47 +0200 (CEST)") Message-ID: <87wqnda0tm.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-08/txt/msg00107.txt.bz2 Mark> Except for one tiny question. How much free space do I need to clone Mark> the future gdb repo and do useful work with it? Some of my machines Mark> don't have a lot of free disk space. Sparse checkouts don't really Mark> work. And it seems you can't do any real development from a shallow Mark> clone. So if the answer to the my question is that I need at least 1G Mark> of disk space, then there is a problem. gdb.git is 372M. That's the bare repository, so no checkout. It may be a bit bigger when we mix in binutils, though the final numbers will all be different for a variety of reasons. I think 400M is an ok rough estimate. I think you have several options here. I believe you can push from a --single-branch clone. One of these weighed in at 304M for me. That was a checkout, not a bare repository. Note that a gdb+binutils checkout from CVS is 321M. So I think that, whatever the issue is, it will be at the margin. Alternatively, you can adopt a more laborious approach by doing a shallow clone on a space-constrained device, and shipping the results to a push-capable repository. I've done this at times (not due to space but because I couldn't conveniently push from the machine I was hacking on). Or, maybe you can run git-cvs locally and cvs commit from your space constrained device into your git repository. I have never tried this. Tom