Received: from spf1.us4.outblaze.com (spf1.us4.outblaze.com [205.158.62.23]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id i9RMMbj3003300 for ; Wed, 27 Oct 2004 22:22:38 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf1.us4.outblaze.com (Postfix) with ESMTP id 3DB1053AAA for ; Wed, 27 Oct 2004 22:22:38 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CMwJT-0005eq-VI for migo@homemail.com; Wed, 27 Oct 2004 18:30:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CMwJ0-0005eb-0w for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 18:30:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CMwIz-0005eP-Jw for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 18:30:09 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CMwIz-0005eM-Gi for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 18:30:09 -0400 Received: from [129.88.30.1] (helo=imag.imag.fr) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CMwAz-0005J3-T3 for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 18:21:54 -0400 Received: from ecrins.imag.fr (ecrins.imag.fr [129.88.43.124]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id i9RMB3AR022490; Thu, 28 Oct 2004 00:11:03 +0200 (CEST) Received: from moy by ecrins.imag.fr with local (Exim 3.35 #1) id 1CMw0V-0006JS-00; Thu, 28 Oct 2004 00:11:03 +0200 To: Thomas Lord References: <20041025210724.GA19744@merconline.com> <200410272144.i9RLiYnd074868@xl2.seyza.com> From: Matthieu Moy Mail-Followup-To: Thomas Lord , jblack@merconline.com, gnu-arch-users@gnu.org Date: Thu, 28 Oct 2004 00:11:03 +0200 In-Reply-To: <200410272144.i9RLiYnd074868@xl2.seyza.com> (Thomas Lord's message of "Wed, 27 Oct 2004 14:44:34 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Thu, 28 Oct 2004 00:11:03 +0200 (CEST) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information Cc: gnu-arch-users@gnu.org, jblack@merconline.com Subject: [Gnu-arch-users] Re: Potential flaw in patch-log pruning in proposal X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1399 Lines: 45 Thomas Lord writes: > So: how about we modify the process so that we maintain a file > > ./src/tla/=merged > > Each time a (log-pruned) version is merged into tla, it's version name > will be appended to that file. No version name should appear twice > in that file. Wouldn't it be better to let (a future version of) tla maintain this file, and integrate it in the arch protocol instead of some user convention? (I think you had another proposal on how to avoid log pruning, but I don't remember exactly what it was) If I take the example of the Xtla project, on a freshly checked-out project, I get this: $ du -sh 8.7M . $ du -sh \{arch}/xtla/ 7.4M {arch}/xtla So, the patch-log takes 85% of the disk space (7 times more than the source files !!). If I take only the list of merged patches in a file, it goes down to 120Kb, which is around 10% of the source size. Another option would be to have a .tar.gz file of the patch-log. On Xtla, this makes a 400Kb compressed file, but I suppose this will make a big performance problem because to answer the question "is changeset X already merged?", tla would have to gunzip the whole file. -- Matthieu _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/