From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: .git/info/refs Date: Wed, 24 Jan 2007 08:41:57 -0800 Message-ID: <45B78C55.2030204@zytor.com> References: <45B70D06.3050506@zytor.com> <45B7818F.6020805@zytor.com> <45B78836.5080508@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jakub Narebski , git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Wed Jan 24 17:42:22 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1H9lCQ-0000nG-WD for gcvg-git@gmane.org; Wed, 24 Jan 2007 17:42:15 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752014AbXAXQmI (ORCPT ); Wed, 24 Jan 2007 11:42:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752006AbXAXQmI (ORCPT ); Wed, 24 Jan 2007 11:42:08 -0500 Received: from terminus.zytor.com ([192.83.249.54]:59836 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752016AbXAXQmG (ORCPT ); Wed, 24 Jan 2007 11:42:06 -0500 Received: from [172.27.0.16] (c-67-180-238-27.hsd1.ca.comcast.net [67.180.238.27]) (authenticated bits=0) by terminus.zytor.com (8.13.8/8.13.7) with ESMTP id l0OGfvWX001056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Jan 2007 08:41:58 -0800 User-Agent: Thunderbird 1.5.0.9 (X11/20061219) In-Reply-To: X-Virus-Scanned: ClamAV 0.88.7/2486/Wed Jan 24 06:47:09 2007 on terminus.zytor.com X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_00, DATE_IN_FUTURE_48_96,RCVD_IN_SORBS_DUL autolearn=no version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on terminus.zytor.com Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Johannes Schindelin wrote: > > Granted, for some things this might work. However, I would not wreak havoc > by changing the format of .git/info/refs, rather put the details you > wanted into .git/info/refs-details. > It's not clear to me if it would be wrecking havoc. After all, if a format can't be expanded *at all*, there is something wrong, and adding things to the end of a line is a common structured way of expansion. Hence the original query > However, for other things (like showing a certain number of commits), it > _might_ make sense to cache them (e.g. when literally thousands of people > look at the 100 last commits of linux-2.6.git), but not for others (e.g. > the 100th last to the 200th last commit of git-tools.git). Any query that's within a repository is fairly easily cachable post-generation. The front page (and its RSS variant) is a bit of an exception, because it involves all repositories at once. Doesn't mean we couldn't do better, but... -hpa