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 iABInMrM027121 for ; Thu, 11 Nov 2004 18:49:23 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf1.us4.outblaze.com (Postfix) with ESMTP id C9C1F53E52 for ; Thu, 11 Nov 2004 18:48:14 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CSK7t-00067d-9K for migo@homemail.com; Thu, 11 Nov 2004 13:56:57 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CSK75-0005yD-5q for gnu-arch-users@gnu.org; Thu, 11 Nov 2004 13:56:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CSK72-0005wj-RG for gnu-arch-users@gnu.org; Thu, 11 Nov 2004 13:56:05 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CSK72-0005wg-P0 for gnu-arch-users@gnu.org; Thu, 11 Nov 2004 13:56:04 -0500 Received: from [205.149.2.136] (helo=xl2.seyza.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CSJyT-00024B-JO for gnu-arch-users@gnu.org; Thu, 11 Nov 2004 13:47:14 -0500 Received: from xl2.seyza.com (localhost.seyza.com [127.0.0.1]) by xl2.seyza.com (8.12.10/8.12.10) with ESMTP id iABIqYIb098589; Thu, 11 Nov 2004 10:52:34 -0800 (PST) (envelope-from lord@xl2.seyza.com) Received: (from lord@localhost) by xl2.seyza.com (8.12.10/8.12.10/Submit) id iABIqX0p098586; Thu, 11 Nov 2004 10:52:33 -0800 (PST) (envelope-from lord) Date: Thu, 11 Nov 2004 10:52:33 -0800 (PST) Message-Id: <200411111852.iABIqX0p098586@xl2.seyza.com> From: Thomas Lord To: gnu-arch-users@gnu.org In-reply-to: <1100167902.2788.38.camel@stargate> (message from Catalin Marinas on Thu, 11 Nov 2004 10:11:43 +0000) Subject: Re: [Gnu-arch-users] Re: darcs vs tla References: <20041107234609.7bf0abfe@delta.hk.office.outblaze.com> <877jowbl8w.fsf@tleepslib.sk.tsukuba.ac.jp> <200411082327.iA8NRVMB084815@xl2.seyza.com> <1099996596.2900.96.camel@stargate> <200411102047.iAAKlUmv093629@xl2.seyza.com> <1100167902.2788.38.camel@stargate> 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: 1509 Lines: 36 > From: Catalin Marinas > > I opened my mind for this darcs thread and it looks like I'm going to > > wind up where I started: they have some rather esoteric merge > > technology that could be added to arch; > Maybe time will tell if this merge technology brings many benefits. I > can think of cases where it is unsafe (see the beginning of this > message). On the other hand, darcs can notify you that the patch > actually depends on a different patch and can pull both at a time. Arch > could track this but it is time consuming with the actual structure of a > changeset (the log or other file should have some information about the > files modified and the corresponding line numbers, without the actual > data added/removed). It could use the revision library as well but it > still means retrieving all the patches to create the full history in a > revlib. Anyway, darcs is not so good at this since it loads all the > patches into memory. Just incidentally: if I did want to spend a lot of time thinking about how to move darcs merge operator to arch i would spend at least part of that time thinking about mappings in which darcs changesets map onto arch versions, not arch revisions. -t _______________________________________________ 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/