From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric S. Raymond" Newsgroups: gmane.emacs.devel Subject: Re: VC mode and git Date: Wed, 25 Mar 2015 12:47:18 -0400 Organization: Eric Conspiracy Secret Labs Message-ID: <20150325164718.GB24458@thyrsus.com> References: <20150324163714.GA27775@thyrsus.com> <83y4mmpb1n.fsf@gnu.org> <20150324173536.GA30608@thyrsus.com> <83twxap92g.fsf@gnu.org> <20150324181936.GA31705@thyrsus.com> Reply-To: esr@thyrsus.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1427302103 26114 80.91.229.3 (25 Mar 2015 16:48:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 25 Mar 2015 16:48:23 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 25 17:48:13 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 1YaoTR-0004PE-3q for ged-emacs-devel@m.gmane.org; Wed, 25 Mar 2015 17:48:09 +0100 Original-Received: from localhost ([::1]:40244 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YaoTQ-0006wE-Ax for ged-emacs-devel@m.gmane.org; Wed, 25 Mar 2015 12:48:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YaoTC-0006w7-Ul for emacs-devel@gnu.org; Wed, 25 Mar 2015 12:47:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YaoTB-0008PE-UB for emacs-devel@gnu.org; Wed, 25 Mar 2015 12:47:54 -0400 Original-Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5]:49395 helo=snark.thyrsus.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YaoT7-0008Ot-Bl; Wed, 25 Mar 2015 12:47:49 -0400 Original-Received: by snark.thyrsus.com (Postfix, from userid 1000) id BB105C00A6; Wed, 25 Mar 2015 12:47:18 -0400 (EDT) Content-Disposition: inline In-Reply-To: X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.23 (2014-03-12) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 71.162.243.5 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:184232 Archived-At: Richard Stallman : > > Even when a remote has been declared, git cannot know about any sequence of > > commits whether it's intended to be published to that remote. It might be > > exploratory programming, done with the option to reset to a prior state > > in mind. > > 1. If that's what you want, why do a commit? You can test the modified > files without committing them. Because quite frequently, while exploring, there are states you want to save - so you can roll back to them - that are not final. For example, a refactor (which should have its own change comment) during an attempted fix. > 2. That is rather sophisticated use; a user who might want to do this > would know how to get what he wants. He could set a flag saying > that C-x v v should not push in this repository, or whatever it takes. He does know how to get what he wants. He gets it by not pushing until he is ready to commit. Separating these operations is the simplest possible way to afford this flexibility. Adding policy flags adds complexity and should not be done unless they bring a larger gain in utility, which is I'm theoretically possible but I'm not seeing. What people are trying to tell you is that you are trying to force-fit a DVCS into behaving like a centralized VCS because your thinking about how to use it is still limited by old mental habits from RCS/CVS days. Early in my learning process about DVCSes I had the same problem and had to get past it. Now it's your turn. -- Eric S. Raymond