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 j0BLC0TI027935 for ; Tue, 11 Jan 2005 21:12:01 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf1.us4.outblaze.com (Postfix) with ESMTP id 898B429875E for ; Tue, 11 Jan 2005 21:12:14 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CoTUp-0004ap-0y for migo@homemail.com; Tue, 11 Jan 2005 16:24:11 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CoTTZ-0004FH-2h for gnu-arch-users@gnu.org; Tue, 11 Jan 2005 16:22:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CoTTS-0004Ad-5s for gnu-arch-users@gnu.org; Tue, 11 Jan 2005 16:22:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CoTTR-00048n-PJ for gnu-arch-users@gnu.org; Tue, 11 Jan 2005 16:22:45 -0500 Received: from [207.115.63.101] (helo=pimout2-ext.prodigy.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CoTFn-00042K-V8 for gnu-arch-users@gnu.org; Tue, 11 Jan 2005 16:08:40 -0500 Received: from www7.prodigy.net (www7-ext.prodigy.net [207.115.61.21]) by pimout2-ext.prodigy.net (8.12.10 milter /8.12.10) with SMTP id j0BL8ddc159924 for gnu-arch-users@gnu.org; Tue, 11 Jan 2005 16:08:39 -0500 To: gnu-arch-users@gnu.org Message-Id: Date: Tue, 11 Jan 2005 16:08:38 -0500 From: "Robert Anderson" Subject: [Gnu-arch-users] branch accounting/status tool 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: 1808 Lines: 54 I think a branch accounting tool that does the following would be useful: You specify a version, and it recursively goes through all of your archives, and finds all versions which were branched from it. For each branch, it figures out if: 1) There are missing patches from the parent 2) There are un-merged patches in the child 3) In each case 1&2, if a star-merge will result in conflicts in either direction It would give a summary listing that looks something like this: proj--main--0 <- -> proj--user--0 (missing and unmerged patches, no conflicts) proj--blah1--0 (missing patches which conflict) proj--fixit--0 (fully up-to-date branch) -> proj--fixit-a--0