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: Fri, 2 Oct 2015 09:37:58 +0300 Message-ID: <560E2646.3010601@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> <560C9B3C.70306@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1443767916 12499 80.91.229.3 (2 Oct 2015 06:38:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 Oct 2015 06:38:36 +0000 (UTC) Cc: eliz@gnu.org, stephen@xemacs.org, monnier@iro.umontreal.ca, dak@gnu.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 02 08:38:22 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 1Zhtz3-0001p3-To for ged-emacs-devel@m.gmane.org; Fri, 02 Oct 2015 08:38:22 +0200 Original-Received: from localhost ([::1]:57755 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zhtz3-0003tX-0h for ged-emacs-devel@m.gmane.org; Fri, 02 Oct 2015 02:38:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46501) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zhtyn-0003tR-Rn for emacs-devel@gnu.org; Fri, 02 Oct 2015 02:38:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zhtyi-0000qk-Oc for emacs-devel@gnu.org; Fri, 02 Oct 2015 02:38:05 -0400 Original-Received: from mail-la0-x230.google.com ([2a00:1450:4010:c03::230]:32992) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zhtyi-0000qd-HS; Fri, 02 Oct 2015 02:38:00 -0400 Original-Received: by laddd9 with SMTP id dd9so190135lad.0; Thu, 01 Oct 2015 23:37:59 -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=1spavxXBSrPupw5Q7RdocKS+58y7Eq59wxFPsMmJVwM=; b=c92Kl2ow3FkoLar/nxYvT+8zUeaUFtFTUBq5oA4I2Ekrthynm7lDuJ1Y8ZDsCNu0AS nQ20CdZLfJxHJFj7iz6LHSchlzDdzGyx7tpaVF3V3o4g1l+C6FNKeuZlWqhBuAeuYC9H kQraA3qgxdkTEK4fcEoTdvAqPSt8wLI2bdhPsw96sluC7+Lxe/doBUrh7V3AfGocy8+D AhUyfubLAiAgKGRmq1mslz5utCqyGKGhlxc6XbUQT6ihFvvDUotNaO0sMkqilb3TNQFO H7HwAZSbrUbyqZWj9sohK30zuygUiE0/Cgx6XtvHc16DCRl+ZVyuYBwVuv1Z+sTlXP4U aDMA== X-Received: by 10.112.13.136 with SMTP id h8mr4587226lbc.23.1443767879852; Thu, 01 Oct 2015 23:37:59 -0700 (PDT) Original-Received: from [192.168.1.190] ([178.252.127.222]) by smtp.googlemail.com with ESMTPSA id a188sm1243787lfa.9.2015.10.01.23.37.58 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 23:37:58 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Thunderbird/41.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::230 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:190643 Archived-At: On 10/02/2015 05:27 AM, Richard Stallman wrote: > > Please elaborate: do you really benefit from the ability to lock the > > file in advance? > > No, I didn't know about that feature. The message said "locking", > so I tought it meant locking by checkout. See e.g. vc-steal-lock. It's only used in vc-next-action. If you don't use RCS in a multi-level environment, same as Eli, and nobody else does, we don't really need that locking feature, and so we don't need vc-next-action to "steal the lock" as a separate step. We don't need that function, and we don't need the `steal-lock' backend command. If RCS demands that a file is locked to the current user before committing (I'm not sure), vc-rcs-checkin could do that.