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: VC command for showing outgoing changes Date: Tue, 13 Oct 2009 16:52:18 -0400 Message-ID: References: <200910132024.n9DKOHGj015040@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 1255467613 19390 80.91.229.12 (13 Oct 2009 21:00:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Oct 2009 21:00:13 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 13 22:59:54 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 1MxoTJ-0007Ya-Lb for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2009 22:59:53 +0200 Original-Received: from localhost ([127.0.0.1]:43647 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxoTJ-0003YM-9X for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2009 16:59:53 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxoMA-0007HA-NH for emacs-devel@gnu.org; Tue, 13 Oct 2009 16:52:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxoM6-0007EV-4Z for emacs-devel@gnu.org; Tue, 13 Oct 2009 16:52:30 -0400 Original-Received: from [199.232.76.173] (port=54152 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxoM6-0007ES-1S for emacs-devel@gnu.org; Tue, 13 Oct 2009 16:52:26 -0400 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:48582) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxoM5-0004Vq-MW for emacs-devel@gnu.org; Tue, 13 Oct 2009 16:52:25 -0400 Original-Received: from faina.iro.umontreal.ca (faina.iro.umontreal.ca [132.204.26.177]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id n9DKqID5027295; Tue, 13 Oct 2009 16:52:19 -0400 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id DA9FF3A07F; Tue, 13 Oct 2009 16:52:18 -0400 (EDT) In-Reply-To: <200910132024.n9DKOHGj015040@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Tue, 13 Oct 2009 13:24:17 -0700 (PDT)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV3383=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:116118 Archived-At: > It would be nice to have a VC command for showing the outgoing changes > for distributed VC systems (i.e. the log of the changes that will be > pushed when you do a VC push). > Let's call this method vc-outgoing (name suggestions are welcome). I think before that we should have support for a `push' backend operation. > vc-hg-outgoing does this, but it's only for mercurial, it would be good > to have a generic method for doing such a thing. Agreed. > vc-outgoing cannot quite use that because most commands that are defined > for log-view-mode do not make sense (annotate, next/previous file, show > version). The next/previous file seem to make just as much (or as little) sense for this as for log-view. Also, why don't annotate and show-version make sense? > One thing we can do is to create a log-view-base-mode and have > log-view-mode and log-view-outgoing-mode derive from this mode, and have > log-view-mode and log-view-outgoing-mode define their own commands and > key bindings. Since each backend typically creates its own vc--log-view-mode, that tend to lead to the need for "multiple inheritance" in define-derived-mode. Given the lack of support for such a monster right now, we should probably stick to something simpler, e.g. add a log-view-outgoing binary var, behaving kind of like a minor-mode and controlling availability of some extra bindings. > Something similar can be done for incoming changes. Indeed. Stefan