From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754229Ab1AUIdU (ORCPT ); Fri, 21 Jan 2011 03:33:20 -0500 Received: from mail-ew0-f46.google.com ([209.85.215.46]:33797 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751755Ab1AUIdT (ORCPT ); Fri, 21 Jan 2011 03:33:19 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=MzrKBixPaPkcdiR4M3uIuEQ5rDYm/FMBy82LHjFgn454jjmrSJzvpysWB6t2Vuy82A tqmgluXRKmL8CK0/Q3iXDT5LDWKy4xxcvI8lqmZhQ9Ib0biQk+z59b46IIjPfZ+CYinZ l7SO5IVUId3wLDpES79ttFbP+ub7TwN6wlF8I= Date: Fri, 21 Jan 2011 10:24:02 +0200 From: Alexey Dobriyan To: nobody Cc: Linus Torvalds , Linux Kernel Mailing List Subject: Re: tag&track [Re: Linux 2.6.38-rc1] Message-ID: <20110121082402.GA4689@p183.telecom.by> References: <1161CC5A-C8CA-477E-B2CE-7870F8E634EE@gmail.com> <20110119051049.GA2536@WALL-E> <20110121032310.GA28289@WALL-E> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110121032310.GA28289@WALL-E> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 20, 2011 at 10:23:10PM -0500, nobody wrote: > On Tue, Jan 18, 2011 at 09:42:42PM -0800, Linus Torvalds wrote: > > On Tue, Jan 18, 2011 at 9:10 PM, nobody wrote: > > > > > > i wish i could do that for everything. i am pulling up to 500MiB every > > > -rc cycle and mostly codes for hardwares i don't have. > > > > No you're not. > > ... i was lying. > > > So no, you're not pulling 500MiB every -rc cycle, unless you're doing > > something stupid like using http (which will trigger a re-fetch, since > > I end up repacking a couple of times a release) or always re-cloning. > > re-cloning to reclaim disk space. but disk space is not the only thing; > i can compile a tar release all in ram (1G) but re-cloning 388M into a > build directory there is a no go. git-clone -s sheesh...