Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id i9S2Xsld003746 for ; Thu, 28 Oct 2004 02:33:54 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf3.us4.outblaze.com (Postfix) with ESMTP id 95F8253AD9 for ; Thu, 28 Oct 2004 02:33:55 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CN0Ef-0005Lo-P2 for migo@homemail.com; Wed, 27 Oct 2004 22:41:57 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CN0EG-0005JO-Tr for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 22:41:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CN0EG-0005JC-Ga for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 22:41:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CN0EG-0005J9-AG for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 22:41:32 -0400 Received: from [209.158.45.74] (helo=linuxguru.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CN06A-0001Vj-BT for gnu-arch-users@gnu.org; Wed, 27 Oct 2004 22:33:10 -0400 Received: by linuxguru.net (Postfix, from userid 10) id 32F4C3B402B; Wed, 27 Oct 2004 22:33:09 -0400 (EDT) Received: by comet.merconline.com (Postfix, from userid 1000) id 876A91436C5; Wed, 27 Oct 2004 22:32:54 -0400 (EDT) To: gnu-arch-users@gnu.org Subject: Re: [Gnu-arch-users] Re: Potential flaw in patch-log pruning in proposal In-Reply-To: <418023CD.1000504@johnmeinel.com> References: <20041025210724.GA19744@merconline.com> <200410272144.i9RLiYnd074868@xl2.seyza.com> <418023CD.1000504@johnmeinel.com> Mail-Folloup-To: never Mail-Copies-To: never Date: Wed, 27 Oct 2004 22:32:54 -0400 Message-Id: <20041028023254.876A91436C5@comet.merconline.com> From: jblack@merconline.com (James Blackwell) 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: 1614 Lines: 48 John Meinel wrote: > > I think the idea that the patch name gets kept, but you can optionally > keep the patch-log itself is a good idea. So the '{arch}/=merged' file > would contain the equivalent of > tla logs --merges There's a catch to doing this. I've meant to (and put off for) quite a bit to build a command that lets you easily see in which revisions a "file" was changed. > Or possibly with the summaries as well. (This isn't as important, and > might cause file size to go up again.) > > Then when tla wants to check if a patch has already been merged, it can > look for the patch-log, and secondly look for the entry in =merged. Aye. I think this would be "good enough" for replay --skip-present. > It might be nicer if =merged was some sort of indexed file format, so > that lookups could be faster, but greping even a 120K file doesn't seem > very expensive. Though I'm in favor of this, actually it can get to be quite a bit more expensive than this. Though it wouldn't be this bad for small/medium sized projects, larger heavily developed projects will see a concatenated patch-log on the order of 5-6 megabytes per working copy/revision in the library. -- James Blackwell Try something fun: For the next 24 hours, give Smile more! each person you meet a compliment! GnuPG (ID 06357400) AAE4 8C76 58DA 5902 761D 247A 8A55 DA73 0635 7400 _______________________________________________ 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/