From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req. Date: Mon, 06 Jan 2014 15:53:28 +0100 Organization: Organization?!? Message-ID: <87y52tupp3.fsf@fencepost.gnu.org> References: <20140102095347.6834E381D0C@snark.thyrsus.com> <87fvp6bdd9.fsf_-_@ktab.red-bean.com> <8761q1ljny.fsf@gmail.com> <20140103175006.GE17261@thyrsus.com> <87ppo6u3mr.fsf@mid.deneb.enyo.de> <874n5i40th.fsf@mid.deneb.enyo.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1389020109 29759 80.91.229.3 (6 Jan 2014 14:55:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 6 Jan 2014 14:55:09 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 06 15:55:13 2014 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 1W0BaC-0006AB-V9 for ged-emacs-devel@m.gmane.org; Mon, 06 Jan 2014 15:55:13 +0100 Original-Received: from localhost ([::1]:35664 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0BaC-0000B5-ME for ged-emacs-devel@m.gmane.org; Mon, 06 Jan 2014 09:55:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0BYy-00078M-JD for emacs-devel@gnu.org; Mon, 06 Jan 2014 09:54:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W0BYs-0004Zr-Pp for emacs-devel@gnu.org; Mon, 06 Jan 2014 09:53:56 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:43820) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0BYs-0004ZQ-I1 for emacs-devel@gnu.org; Mon, 06 Jan 2014 09:53:50 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W0BYj-0003Vp-TK for emacs-devel@gnu.org; Mon, 06 Jan 2014 15:53:41 +0100 Original-Received: from x2f5214e.dyn.telefonica.de ([2.245.33.78]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 06 Jan 2014 15:53:41 +0100 Original-Received: from dak by x2f5214e.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 06 Jan 2014 15:53:41 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 40 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f5214e.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:lTuRcqBQcNGu/Z8AdKp16pQur1Y= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:167465 Archived-At: Richard Stallman writes: > I never consult changelog files if I have the full VCS history. > > I do. I use the ChangeLog files to see what changes affected a > certain function. I tend to use C-x v g for that (it maps to git blame). Its drawback is that it also reflects whitespace changes, but then it's easy to navigate across them with the proper keybindings (usually A) until finding the change one is looking for, then getting the corresponding log with l. > Then I use VC history to look at the changes that are relevant to the > issue. I'm not saying that this is an "invalid" workflow. However, the generic VC support of Emacs allows, when coupled with a version control system that is reasonably fast, to use alternate workflows that do not suffer from significant drawbacks compared to the benefits from not having to maintain manual ChangeLog files separately. This is not specific to Git (actually, it was already available in CVS). What is noticeable, however, is that Git's performance does not make this a waiting game, and that Git is often able to track the origin of lines even when material was rearranged beyond the renaming of files. Git offers several options for the amount of history searching it should perform: what is intransparent is just which options vc.el happens to be using and how one can change them in case something goes wrong. In general, it's more often than not the case that Git finds out more than one expected, but when the reverse happens, vc-git does not make it easily discoverable how one can tell Git to search more thoroughly. I digress: what I wanted to say is that one gets a few tools (and with an Emacs interface) that work reasonably well for addressing most of the tasks one would otherwise use a ChangeLog to get done. -- David Kastrup