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 19:32:57 +0300 Message-ID: <560EB1B9.40700@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> <83si5t7njo.fsf@gnu.org> <83zj015quz.fsf@gnu.org> <560E959A.4070905@yandex.ru> <83mvw15o5s.fsf@gnu.org> <560E9A8C.9060607@yandex.ru> <83lhbl5nan.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 1443805569 8662 80.91.229.3 (2 Oct 2015 17:06:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 Oct 2015 17:06:09 +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 Fri Oct 02 19:06:02 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 1Zi3mU-00036F-A4 for ged-emacs-devel@m.gmane.org; Fri, 02 Oct 2015 19:06:02 +0200 Original-Received: from localhost ([::1]:33692 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi3mS-0000n8-LC for ged-emacs-devel@m.gmane.org; Fri, 02 Oct 2015 13:06:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55813) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi3Gb-0005oZ-R5 for emacs-devel@gnu.org; Fri, 02 Oct 2015 12:33:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zi3GW-0004BW-Qp for emacs-devel@gnu.org; Fri, 02 Oct 2015 12:33:05 -0400 Original-Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]:34161) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi3GW-0004BJ-LB; Fri, 02 Oct 2015 12:33:00 -0400 Original-Received: by wicfx3 with SMTP id fx3so41279412wic.1; Fri, 02 Oct 2015 09:33:00 -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=WaM3CGjkT+Ap5nmqmNpNF4LsaSffrw9VvMduIkhJkvM=; b=RboerFn9uVedGYTEjDvA+TLROykr7JumEKEdwt/BozGJ/b0Unt0ekMCtU6DYOhpvBm oTU0j/x4B140uxMG/kreqFWZmI5COl4ZdvQPfsFfuHn6QbsC8C4bf9QO1cqqpefaM/Ry ufAoc2mfWR1qo8paUUY2ywiEprISmsN9iU24SL1pcbc5GeqIC0pCM4Wn274AVlUiZXS3 9CXWQaOv3OUJoy3K8LOy4BUEyvQc7pCFDcbSn+yaCIdSlfG6jrmRPzNGVQIU+MaSYLKA zwqcrLrlDHKG1nt0SKurMl0v0w0c9ynEzeTczNrysaovHoQGxAzE52LSfuI0G9akslBi qp3Q== X-Received: by 10.194.121.100 with SMTP id lj4mr17146486wjb.104.1443803580044; Fri, 02 Oct 2015 09:33:00 -0700 (PDT) Original-Received: from [10.9.0.103] (nat.webazilla.com. [78.140.128.228]) by smtp.googlemail.com with ESMTPSA id hx4sm12103913wjb.31.2015.10.02.09.32.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Oct 2015 09:32:58 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Thunderbird/41.0 In-Reply-To: <83lhbl5nan.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::22d 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:190725 Archived-At: On 10/02/2015 05:59 PM, Eli Zaretskii wrote: > We are talking about what vc-next-action _should_ do. I'm saying that > it would make sense for it to always check whether update is needed, > or maybe even actually do it. In addition to problems Stefan mentioned (can't commit without pulling; a pull can fail), that would be a speed bump. And "pull before committing" is non-idiomatic Git workflow, so we probably shouldn't use it by default either way.