From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: limit the number of log entries displayed by C-x v l Date: Fri, 13 Nov 2009 09:10:55 -0500 Message-ID: References: <200911122319.nACNJvUn006154@godzilla.ics.uci.edu> <200911130221.nAD2Lu4q007527@godzilla.ics.uci.edu> <200911130502.nAD52OVv008802@godzilla.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1258121476 971 80.91.229.12 (13 Nov 2009 14:11:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Nov 2009 14:11:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 13 15:11:09 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N8wrl-0006pG-5D for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2009 15:11:09 +0100 Original-Received: from localhost ([127.0.0.1]:53671 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8wrk-0001p5-Dp for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2009 09:11:08 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N8wre-0001oJ-Ri for emacs-devel@gnu.org; Fri, 13 Nov 2009 09:11:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N8wrZ-0001mP-9G for emacs-devel@gnu.org; Fri, 13 Nov 2009 09:11:01 -0500 Original-Received: from [199.232.76.173] (port=58497 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8wrZ-0001mF-47 for emacs-devel@gnu.org; Fri, 13 Nov 2009 09:10:57 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:57541 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N8wrY-0006cr-K2 for emacs-devel@gnu.org; Fri, 13 Nov 2009 09:10:56 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAP/3/EpFpYg5/2dsb2JhbACBTdQMhDwEgW2HR4J5 X-IronPort-AV: E=Sophos;i="4.44,737,1249272000"; d="scan'208";a="49349867" Original-Received: from 69-165-136-57.dsl.teksavvy.com (HELO pastel.home) ([69.165.136.57]) by ironport2-out.pppoe.ca with ESMTP; 13 Nov 2009 09:10:55 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 56F487F82; Fri, 13 Nov 2009 09:10:55 -0500 (EST) In-Reply-To: <200911130502.nAD52OVv008802@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Thu, 12 Nov 2009 21:02:24 -0800 (PST)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116943 Archived-At: >> > With the proposed backend change that just needs >> > vc-annotate-show-log-revision-at-line to pass a 1 as the last argument >> > to vc-print-log-internal. >> Assuming we retarget the `working-revision' argument to specify the >> "starting" revision, I guess. Yes, that could work. > Actually, after looking a bit more we'd need more changes, the > `working-revision' is not passed to the `print-log' VC method, so a bit > more work would be needed for that :-( > But this does not affect my original proposal, which is still needed. Yes, I'm not opposing it, I'm just trying to get a better general picture. Some of the problems we may encounter is that some backends don't support the `limit' argument. Hopefully all those backends can easily turn a "print-log FILE REV LIMIT=1" request into "print-log FILE REV1 REV2" instead, tho. Not sure what to do for other values of LIMIT, but maybe that's doable as well. > We show the terse log for directories already, but there's no way to > expand it (yet). But even when using the terse log, there's still a > need to limit the log size. That's my impression a well, Stefan