From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: RCS, again: another removed functionality: undo last-checkin Date: Thu, 1 Oct 2015 22:43:20 +0300 Message-ID: <560D8CD8.7080307@yandex.ru> References: <87oagx6tzz.fsf@mat.ucm.es> <55FF4026.2050004@yandex.ru> <83si68nu4i.fsf@gnu.org> <87eghsfd3m.fsf@fencepost.gnu.org> <83k2rknr2c.fsf@gnu.org> <87mvwellmg.fsf@uwakimon.sk.tsukuba.ac.jp> <56023A6C.3020302@yandex.ru> <5602BE3E.1050009@yandex.ru> <5602C4DE.8020105@yandex.ru> <560B4899.2070708@yandex.ru> <83wpv8be0x.fsf@gnu.org> <83mvw4b871.fsf@gnu.org> <560BC90B.1040902@yandex.ru> <83eghgatxa.fsf@gnu.org> <560C9BB7.2070408@yandex.ru> <83wpv79iel.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1443729150 10772 80.91.229.3 (1 Oct 2015 19:52:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Oct 2015 19:52:30 +0000 (UTC) Cc: stephen@xemacs.org, dak@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 01 21:52:24 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zhjtv-0001Pg-Dd for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2015 21:52:23 +0200 Original-Received: from localhost ([::1]:55930 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zhjtu-0006WQ-NB for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2015 15:52:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhjlH-0006J1-Hr for emacs-devel@gnu.org; Thu, 01 Oct 2015 15:43:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZhjlE-0003m1-9G for emacs-devel@gnu.org; Thu, 01 Oct 2015 15:43:27 -0400 Original-Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:38784) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhjlE-0003l0-30; Thu, 01 Oct 2015 15:43:24 -0400 Original-Received: by wiclk2 with SMTP id lk2so4074739wic.1; Thu, 01 Oct 2015 12:43:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=twKJeF7r8lFJDCrNn4lRIkmkr1EBteuhutRzmfjTsWQ=; b=OcbCEIZji57LcQ9h3GxsfEAjkAO1c+WkAeM1bsKqqiq/iTLhYxMi9jZ7Vqaitfz4Ze 7ejekyO65lKFH780xk247kZzqooYcx/OWijZntdnr5OPgx/9KHv4KPqlyh2HnjXqu2vd InCR3xrZLyAJKOfSaCaCv4399Sxwiohl0I/0z3EEc00OHb+nWyypBQXEWSFaotk9zPlU XomYbL4PUlRZ9i/FExGEbqGh7yXTAe6QbmOqpJzShg+pmvyjm0xsa1OdKtEyh6WDj3hy AEk2xayY7IZFoI1x4lSHp1oCSjqk08CelmDSR0MLYfwVhuBQhCBQcbkbc7S9aeu4f/OW m7gQ== X-Received: by 10.194.117.39 with SMTP id kb7mr11866692wjb.129.1443728603423; Thu, 01 Oct 2015 12:43:23 -0700 (PDT) Original-Received: from [10.9.0.103] (nat.webazilla.com. [78.140.128.228]) by smtp.googlemail.com with ESMTPSA id r9sm7676583wjz.35.2015.10.01.12.43.21 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 12:43:22 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Thunderbird/41.0 In-Reply-To: <83wpv79iel.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:190586 Archived-At: On 10/01/2015 10:06 AM, Eli Zaretskii wrote: >>> Maybe we should simply leave the locking VCSes out of this. People >>> who use those back-ends have used vc-next-action for a long time, so I >>> guess they won't really need vc-steal-lock. > AFAICS, "C-x v c" and "C-x v C" are both available, and should be good > candidates for vc-checkin, I think. Thinking back to your argument that "For a centralized version control system, if any work file in the VC fileset is out of date, offer to update the fileset" still makes sense, it sounds like we should use a more complex `vc-commit' that would incorporate that step, as well as the checkin action itself. Further, creating a new binding for `vc-commit' looks like a half-measure. If we intend it to be used more, it should occupy the easier to hit key sequence (C-x v v). If we agree on that, there are several options for vc-next-action. Either find it a new binding, or remove its binding altogether a take care of locking backends some other way (either with a dedicated vc-steal-lock command, or by locking right before committing, like explained previously). To my (obviously) limited knowledge, RMS is the only user of a locking backend, and so far he hasn't answered the pertinent question about his workflow.