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: Mon, 21 Sep 2015 22:18:41 +0300 Message-ID: <83lhbzmvhq.fsf@gnu.org> References: <87oagx6tzz.fsf@mat.ucm.es> <55FF4026.2050004@yandex.ru> <83si68nu4i.fsf@gnu.org> <56000DEB.1000306@yandex.ru> <83si67n4ch.fsf@gnu.org> <5600373A.6090206@yandex.ru> <83oagvn1lz.fsf@gnu.org> <56003D57.2080102@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1442863149 1315 80.91.229.3 (21 Sep 2015 19:19:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Sep 2015 19:19:09 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 21 21:19:01 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 1Ze6c8-0005H0-HD for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2015 21:19:00 +0200 Original-Received: from localhost ([::1]:60699 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ze6c7-0004SV-UO for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2015 15:18:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60399) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ze6c3-0004SF-Qg for emacs-devel@gnu.org; Mon, 21 Sep 2015 15:18:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ze6c0-0005Bi-Lg for emacs-devel@gnu.org; Mon, 21 Sep 2015 15:18:55 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:35128) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ze6c0-0005BT-EH for emacs-devel@gnu.org; Mon, 21 Sep 2015 15:18:52 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NV100700K2FA300@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Mon, 21 Sep 2015 22:18:31 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NV10075WKAU9F20@a-mtaout20.012.net.il>; Mon, 21 Sep 2015 22:18:31 +0300 (IDT) In-reply-to: <56003D57.2080102@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.166 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:190209 Archived-At: > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Mon, 21 Sep 2015 20:24:39 +0300 > > On 09/21/2015 08:06 PM, Eli Zaretskii wrote: > > > But what about CVS? Its "rollback" command does remove the commit > > upstream. > > CVS has a "rollback" command? Yes, it does. From the description of "cvs admin": admin options ------------- [...] `-oRANGE' Deletes ("outdates") the revisions given by RANGE. (It then goes on to describe the syntax of RANGE, basically REV1::REV2.) > But if it does, sure, that's exactly what I mean. > > > Going from RCS to Git needs some generalization, so if Git's rollback > > will affect the remote, when it should, it's OK, I think. > > It won't. That would be doubly dangerous. So is "cvs -o". The CVS manual says that much. Why should Git be different? A careful user won't invoke this command unless they know what they are doing, right? > 'git revert', by itself, doesn't affect the remote either. Indeed, so what is the reason not to use it as "rollback"? > Like I said, for CVS/RCS/SVN commands (which unavoidably affect the > remote, because there's no "local" repository), the correspondent > commands in Git/Hg/Bzr will only act on the local repository. > > We have `vc-push' for propagating those changes upstream. I agree. But the original issue was whether a "rollback" should invoke "git reset --hard", "git revert", or sometimes one and sometimes the other. The issue never was about adding a "push" to that.