From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kay Sievers" Subject: Re: gitweb: kernel versions in the history (feature request, probably) Date: Wed, 21 Nov 2007 17:06:39 +0100 Message-ID: <3ae72650711210806v1e7daa2fq729a7593def99ef7@mail.gmail.com> References: <20071120142042.GA4157@ff.dom.local> <20071120215904.GF1001@machine.or.cz> <47436E0F.6080003@o2.pl> <20071121032009.GB4175@fieldses.org> <20071121075217.GA1642@ff.dom.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "J. Bruce Fields" , "Petr Baudis" , linux-kernel@vger.kernel.org, git@vger.kernel.org To: "Jarek Poplawski" X-From: git-owner@vger.kernel.org Wed Nov 21 17:07:30 2007 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1Ius6Q-0005eY-3E for gcvg-git-2@gmane.org; Wed, 21 Nov 2007 17:07:02 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756737AbXKUQGo (ORCPT ); Wed, 21 Nov 2007 11:06:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756372AbXKUQGn (ORCPT ); Wed, 21 Nov 2007 11:06:43 -0500 Received: from ug-out-1314.google.com ([66.249.92.170]:20747 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756037AbXKUQGl (ORCPT ); Wed, 21 Nov 2007 11:06:41 -0500 Received: by ug-out-1314.google.com with SMTP id z38so133684ugc for ; Wed, 21 Nov 2007 08:06:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=vXKPU8wG8nkHl2/4BMdSxaOXAAMqgeVctwWsb5h2E60=; b=Oh+PCpb/C2yU6vRkrNmB3QTjIoGtvYsYAye4oyS2/sUqL3mkrRodK0K9OoAAHEBPE4Hkh2qKAkbUIMIW6453BMKhcCMwOrDBp+OiAmIBtVmOot/O8hDZBGBAerrnBsJdj1Q0QW/cnvtK0U7HZZbEe0ffs7HMGLKm7138E68Momo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ZvEkGWDtK/lAyKmuOb5vt4Ru18w5D6EVxaSW2a3OJm5ovzthQoZImzuhwOZnF7no5XVrh7bQt0cig+l+x8Pf+Yto4Xi/RiEG8IqyhbQJhYEdx6TPW/yGWlkzdqseAFaMUt8RbY9/ejKkFGIxRrLjLYvbISqm9KPdNrzOiTMNUgg= Received: by 10.66.243.4 with SMTP id q4mr683096ugh.1195661199394; Wed, 21 Nov 2007 08:06:39 -0800 (PST) Received: by 10.66.255.13 with HTTP; Wed, 21 Nov 2007 08:06:39 -0800 (PST) In-Reply-To: <20071121075217.GA1642@ff.dom.local> Content-Disposition: inline X-Google-Sender-Auth: 2c2bf681d6592546 Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On Nov 21, 2007 8:52 AM, Jarek Poplawski wrote: > On Tue, Nov 20, 2007 at 10:20:09PM -0500, J. Bruce Fields wrote: > > On Wed, Nov 21, 2007 at 12:30:23AM +0100, Jarek Poplawski wrote: > > > I don't know git, but it seems, at least if done for web only, this > > > shouldn't be so 'heavy'. It could be a 'simple' translation of commit > > > date by querying a small database with kernel versions & dates. > > > > If I create a commit in my linux working repo today, but Linus doesn't > > merge it into his repository until after he releases 2.6.24, then my > > commit will be created with an earlier date than 2.6.24, even though it > > isn't included until 2.6.25. > > > > So you have to actually examine the history graph to figure this out > > this sort of thing. > > Of course, you are right, and I probably miss something, but to be > sure we think about the same thing let's look at some example: so, I > open a page with current Linus' tree, go to something titled: > /pub/scm / linux/kernel/git/torvalds/linux-2.6.git / history > > and see: > 2007-10-10 Stephen Hemminger [NET]: Make NAPI polling independent ... > and just below something with 2007-08-14 date. > > Accidentally, I can remember this patch introduced many changes, and > this big interval in dates suggests some waiting. Then I look at the > commit, and there are 2 dates visible, so the patch really was created > earlier. Then I go back to: > /pub/scm / linux/kernel/git/torvalds/linux-2.6.git / summary > > and at the bottom I can see this: > > ... > tags > 4 days ago v2.6.24-rc3 Linux 2.6.24-rc3 > 2 weeks ago v2.6.24-rc2 Linux 2.6.24-rc2 > 4 weeks ago v2.6.24-rc1 Linux 2.6.24-rc1 > 6 weeks ago v2.6.23 Linux 2.6.23 > > which drives me crazy, because, without looking at the calendar, and > calculator, I don't really know which month was 6 weeks ago, and 4 > days ago, either! > > So, I go to the: http://www.eu.kernel.org/pub/linux/kernel/v2.6/, > do some scrolling, look at this: > ChangeLog-2.6.23 09-Oct-2007 20:38 3.8M > > and only now I can guess, this napi patch didn't manage to 2.6.23. > Of course, usually I've to do a few more clicks and reading to make > sure where it really started. > > So, this could suggest this 2007-10-10 (probably stored with time > too), could be useful here... but it seems, I'm wrong. > > Of course, this problem doesn't look so hard if we forget about > git internals: I can imagine keeping a simple database, which > could simply retrieve commit numbers from these ChangeLogs, and > connecting this with gitweb's commit page as well... For > performance reasons, doing it only for stable and testing, so with > -rc 'precision' would be very helpful too. The "plain" view of the patch has the "version" included: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=bea3348eef27e6044b6161fd04c3152215f96411 From: Stephen Hemminger Date: Wed, 3 Oct 2007 23:41:36 +0000 (-0700) Subject: [NET]: Make NAPI polling independent of struct net_device objects. X-Git-Tag: v2.6.24-rc1~1454^2~841 Is that what you are looking for? Kay