From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sean" Subject: Re: [PATCH] [RFD] Add repoid identifier to commit Date: Thu, 12 May 2005 06:39:46 -0400 (EDT) Message-ID: <3019.10.10.10.24.1115894386.squirrel@linux1> References: <1115847510.22180.108.camel@tglx> <2780.10.10.10.24.1115848852.squirrel@linux1> <1115849141.22180.123.camel@tglx> <2807.10.10.10.24.1115850254.squirrel@linux1> <1115850619.22180.133.camel@tglx> <2853.10.10.10.24.1115850996.squirrel@linux1> <1115851718.22180.153.camel@tglx> <2883.10.10.10.24.1115852463.squirrel@linux1> <1115854419.22180.196.camel@tglx> <2997.10.10.10.24.1115855049.squirrel@linux1> <1115857838.22180.250.camel@tglx> <3185.10.10.10.24.1115858739.squirrel@linux1> <1115859372.22180.266.camel@tglx> <3259.10.10.10.24.1115859535.squirrel@linux1> <1115892451.16187.561.camel@hades.cambridge.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: tglx@linutronix.de, git@vger.kernel.org X-From: git-owner@vger.kernel.org Thu May 12 12:33:29 2005 Return-path: Received: from vger.kernel.org ([12.107.209.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DWAzH-00054s-R0 for gcvg-git@gmane.org; Thu, 12 May 2005 12:32:16 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261417AbVELKj4 (ORCPT ); Thu, 12 May 2005 06:39:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261409AbVELKj4 (ORCPT ); Thu, 12 May 2005 06:39:56 -0400 Received: from simmts12.bellnexxia.net ([206.47.199.141]:19913 "EHLO simmts12-srv.bellnexxia.net") by vger.kernel.org with ESMTP id S261417AbVELKjr (ORCPT ); Thu, 12 May 2005 06:39:47 -0400 Received: from linux1 ([69.156.111.46]) by simmts12-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050512103946.VFOD19200.simmts12-srv.bellnexxia.net@linux1>; Thu, 12 May 2005 06:39:46 -0400 Received: from linux1 (linux1.attic.local [127.0.0.1]) by linux1 (8.12.11/8.12.11) with ESMTP id j4CAdjQ0010862; Thu, 12 May 2005 06:39:45 -0400 Received: from 10.10.10.24 (SquirrelMail authenticated user sean) by linux1 with HTTP; Thu, 12 May 2005 06:39:46 -0400 (EDT) In-Reply-To: <1115892451.16187.561.camel@hades.cambridge.redhat.com> To: "David Woodhouse" User-Agent: SquirrelMail/1.4.4-2 X-Priority: 3 (Normal) Importance: Normal Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org On Thu, May 12, 2005 6:07 am, David Woodhouse said: > On Wed, 2005-05-11 at 20:58 -0400, Sean wrote: >> > Try to find out the history of kernel.org/.../dwmw2/audit-2.6 in >> > correct order, using the available tools. >> > >> > Come back to me when you are done. >> >> Ask me any question that matters and i'll answer it with available >> tools. > > The above question matters, so please answer it if you can. I'll make it > clearer for you though... > > By 'correct order' Thomas means the order in which my old BK-export > script used to generate the "changesets since last release" web page; > the order in which the changes actually got merged into Linus' > repository. > > If I looked at the page yesterday, and then I look at it again today, I > want all the commits I hadn't seen already to be at the _top_. > Regardless of the date on which they were _originally_ committed to some > private tree elsewhere. > > There were a lot of complaints until I worked out how to get that > ordering out of BitKeeper. > Actually, here is one very simple idea, just use the times from the object files themselves. Now as you descend the hierarchy you can simply stat the object file to get the "local commit time". Just simply stop descending down each branch when you find a commit with a time stamp that is outside the range you're interested in. Sean