From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3923 invoked by alias); 22 Aug 2013 20:10:56 -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 3892 invoked by uid 89); 22 Aug 2013 20:10:55 -0000 X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 22 Aug 2013 20:10:54 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3) with ESMTP id r7MKAmps015198; Thu, 22 Aug 2013 22:10:48 +0200 (CEST) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3/Submit) id r7MKAljG013904; Thu, 22 Aug 2013 22:10:47 +0200 (CEST) Date: Thu, 22 Aug 2013 20:10:00 -0000 Message-Id: <201308222010.r7MKAljG013904@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: tromey@redhat.com CC: gdb@sourceware.org, binutils@sourceware.org In-reply-to: <8738q4gj7a.fsf@fleche.redhat.com> (message from Tom Tromey on Tue, 20 Aug 2013 15:12:41 -0600) Subject: Re: A Proposal to Move to Git References: <8738q4gj7a.fsf@fleche.redhat.com> X-SW-Source: 2013-08/txt/msg00102.txt.bz2 > From: Tom Tromey > CC: Binutils Development > Date: Tue, 20 Aug 2013 15:12:41 -0600 > > I'd like to move gdb and binutils from CVS to Git. I've done much of > the preliminary work and I will do the remainder, including the > inevitable follow-up bug-fixing. I still *hate* git. Hate it even more now that I've used it for a project. It gets in my way; it never does what I want, at least not by default. It's slow; updating a tree takes significantly more time than with cvs as it insists that I stash my local changes first. It's buggy; I had it just sit there and spin forever on a git pull on several occasions. It encourages the annoying "send the gazillian diffs in a series again, just because I've fixed a single spelling mistake in one of them" behaviour. But it seems I'm the only one in the world who doesn't "git" it, so I'll shut up. Except for one tiny question. How much free space do I need to clone the future gdb repo and do useful work with it? Some of my machines don't have a lot of free disk space. Sparse checkouts don't really work. And it seems you can't do any real development from a shallow clone. So if the answer to the my question is that I need at least 1G of disk space, then there is a problem.