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: Mon, 21 Sep 2015 19:58:34 +0300 Message-ID: <5600373A.6090206@yandex.ru> References: <87oagx6tzz.fsf@mat.ucm.es> <55FF4026.2050004@yandex.ru> <83si68nu4i.fsf@gnu.org> <56000DEB.1000306@yandex.ru> <83si67n4ch.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 1442854755 22655 80.91.229.3 (21 Sep 2015 16:59:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Sep 2015 16:59:15 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 21 18:59:10 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 1Ze4Qn-00009s-Sq for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2015 18:59:10 +0200 Original-Received: from localhost ([::1]:59837 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ze4Qn-00010P-2o for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2015 12:59:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ze4Qk-00010I-SO for emacs-devel@gnu.org; Mon, 21 Sep 2015 12:59:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ze4Qf-0008CW-T6 for emacs-devel@gnu.org; Mon, 21 Sep 2015 12:59:06 -0400 Original-Received: from mail-wi0-x232.google.com ([2a00:1450:400c:c05::232]:34171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ze4Qf-0008CR-Lc; Mon, 21 Sep 2015 12:59:01 -0400 Original-Received: by wicfx3 with SMTP id fx3so155719842wic.1; Mon, 21 Sep 2015 09:59:01 -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=lVABVUXAP2aWEneB34WMtcnOQ/JpiIWiTTyWno3D/q8=; b=tOLFtBF6g1v+DHH10T0rVydwvSFNVKpPk5v8RqP08MtM6GDXUhcyse4Lt4yBMm2AoF LRzJqSZQOiB/1pTDTKLkpuzibhCEqcLgMMkVhZUnNnHmLHtAEGPlKbeIqIPZ2vW6PAwf cYgo7QTDuwE/mwX7y7QVsQ88offZBlhSa4miWsWXLSDd77cCDjVvRbbLtINe2+IsQGUd Sx1Tc1Vq8iSVWIJkzUEiAjW9MBJm/9wsl4MdHA55Z1tOPlPknWpTtz8BDRYtKSo3CNtl 6JGACITFD512m7D6ZVDnJ2+IaIDYUNGpuRWCV2peA8+yxDJE6syob2lCErG6+nz+rtKE 9C6Q== X-Received: by 10.180.88.4 with SMTP id bc4mr15705778wib.68.1442854740972; Mon, 21 Sep 2015 09:59:00 -0700 (PDT) Original-Received: from [10.9.0.103] (nat.webazilla.com. [78.140.128.228]) by smtp.googlemail.com with ESMTPSA id xt1sm24988556wjb.32.2015.09.21.09.58.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Sep 2015 09:59:00 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Thunderbird/41.0 In-Reply-To: <83si67n4ch.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::232 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:190199 Archived-At: On 09/21/2015 07:07 PM, Eli Zaretskii wrote: >>> If the commit was already pushed, you will need "git revert" instead, >>> I think. >> >> What does RCS do in this case? > > There's no "push" in RCS. Then I think the correspondence of RCS commands will be Git commands that act similarly on the local repository. Then 'git reset --hard HEAD^' is a better match, because, like someone explained, the point of 'rcs rollback' is to remove the revision in question from history. And if 'git reset' is unsafe, well, 'rcs rollback' doesn't sound particularly safe either. Either way, we need a smart way to detect dangerous operations (e.g. see if affected commits are already published). The "amend" Git capability, which we already support, is unsafe too.