From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: RCS, again: another removed functionality: undo last-checkin Date: Thu, 01 Oct 2015 23:12:00 +0300 Message-ID: <83d1wy8i27.fsf@gnu.org> 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> <560D8CD8.7080307@yandex.ru> <83eghe8ini.fsf@gnu.org> <560D9236.6020008@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1443730374 32408 80.91.229.3 (1 Oct 2015 20:12:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Oct 2015 20:12:54 +0000 (UTC) Cc: stephen@xemacs.org, dak@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 01 22:12:42 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 1ZhkDU-0003zo-Gf for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2015 22:12:36 +0200 Original-Received: from localhost ([::1]:56076 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhkDT-0005BX-RP for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2015 16:12:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38444) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhkDA-00057f-7L for emacs-devel@gnu.org; Thu, 01 Oct 2015 16:12:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZhkD9-0002PW-5B for emacs-devel@gnu.org; Thu, 01 Oct 2015 16:12:16 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:55852) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhkD5-0002Op-6m; Thu, 01 Oct 2015 16:12:11 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NVK00C0056WFO00@a-mtaout22.012.net.il>; Thu, 01 Oct 2015 23:12:09 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NVK00CZQ5G98C80@a-mtaout22.012.net.il>; Thu, 01 Oct 2015 23:12:09 +0300 (IDT) In-reply-to: <560D9236.6020008@yandex.ru> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 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:190591 Archived-At: > Cc: monnier@iro.umontreal.ca, rms@gnu.org, stephen@xemacs.org, dak@gnu.org, > emacs-devel@gnu.org > From: Dmitry Gutov > Date: Thu, 1 Oct 2015 23:06:14 +0300 > > On 10/01/2015 10:59 PM, Eli Zaretskii wrote: > > v and c are neighbors, so I don't see why "C-x v c" would be hard. > > It's not hard, it's harder. Again, if `vc-commit' is going to be the > preferred command, it should use the better binding. The difference is too small to justify breaking old habits, IMO. > Arguing otherwise is discouraging, and it's a good example of why focus > on backward compatibility saps mental energy. Would you prefer I don't > work on this change at all? No, I would prefer that you'd be more willing to compromise at times. > > I ask once again why not make vc-next-action support some simple > > workflow with modern VCSes. > > That's very vague. I described up-thread what I had in mind in more detail: a CVS-like workflow. > >> 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. > > > > If by "locking VCS" you mean RCS, then I use it from time to time. > > Could you answer that question, then? I thought I already did: I always use RCS for files I maintain myself, so other users are not involved, and locking is a no-op.