From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261899AbVDHUuY (ORCPT ); Fri, 8 Apr 2005 16:50:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262953AbVDHUuY (ORCPT ); Fri, 8 Apr 2005 16:50:24 -0400 Received: from fmr22.intel.com ([143.183.121.14]:2214 "EHLO scsfmr002.sc.intel.com") by vger.kernel.org with ESMTP id S261899AbVDHUuL (ORCPT ); Fri, 8 Apr 2005 16:50:11 -0400 Date: Fri, 8 Apr 2005 13:50:04 -0700 Message-Id: <200504082050.j38Ko4r19673@unix-os.sc.intel.com> To: Linus Torvalds From: Luck@unix-os.sc.intel.com, Tony cc: Kernel Mailing List Subject: Re: Kernel SCM saga.. In-Reply-To: <20050408191638.GA5792@taniwha.stupidest.org> References: <20050408041341.GA8720@taniwha.stupidest.org> <20050408071428.GB3957@opteron.random> <4256AE0D.201@tiscali.de> <20050408171518.GA4201@taniwha.stupidest.org> <20050408180540.GA4522@taniwha.stupidest.org> <20050408191638.GA5792@taniwha.stupidest.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org It looks like an operation like "show me the history of mm/memory.c" will be pretty expensive using git. I'd need to look at the current tree, and then trace backwards through all 60,000 changesets to see which ones had actual changes to this file. Could you expand the tuple in the tree object to include a back pointer to the previous tree in which the tuple changed? Or does adding history to the tree violate other goals of the tree type? -Tony