From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: git history tracking across renames (and emacs support) Date: Wed, 03 Jan 2018 17:45:27 -0500 Message-ID: References: <87efnan46u.fsf@linux-m68k.org> <86wp12qtgo.fsf@dod.no> <83tvw6chqv.fsf@gnu.org> <86shbprix7.fsf_-_@dod.no> <83608kck4c.fsf@gnu.org> <544c170f-99bd-c701-3063-c697296a30a6@cs.ucla.edu> <83po6rar9c.fsf@gnu.org> <20180103182917.GC5435@ACM> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1515019469 31910 195.159.176.226 (3 Jan 2018 22:44:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 3 Jan 2018 22:44:29 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 03 23:44:24 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWrli-0007e8-TA for ged-emacs-devel@m.gmane.org; Wed, 03 Jan 2018 23:44:19 +0100 Original-Received: from localhost ([::1]:40059 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWrni-0007St-5a for ged-emacs-devel@m.gmane.org; Wed, 03 Jan 2018 17:46:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59966) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWrmx-0007SJ-CT for emacs-devel@gnu.org; Wed, 03 Jan 2018 17:45:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWrmw-0005wx-IK for emacs-devel@gnu.org; Wed, 03 Jan 2018 17:45:35 -0500 Original-Received: from pmta11.teksavvy.com ([76.10.157.34]:57833) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1eWrmr-0005qm-P0; Wed, 03 Jan 2018 17:45:29 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2GxOQD4W01a/xCds2tdg2+BWolJhgeOE?= =?us-ascii?q?gGCADMBmQuFPwQCAoQvRRMBAQEBAQEBAQEDaCiFJQEEAVYjBQsLDiYSFBgNJIo?= =?us-ascii?q?5CLQvij4BAQgCJoQTiH+LGgWTNZAcl02GGINch3aYQjcigU8yGggwgmeCUh2CB?= =?us-ascii?q?SOKAwEBAQ?= X-IPAS-Result: =?us-ascii?q?A2GxOQD4W01a/xCds2tdg2+BWolJhgeOEgGCADMBmQuFPwQ?= =?us-ascii?q?CAoQvRRMBAQEBAQEBAQEDaCiFJQEEAVYjBQsLDiYSFBgNJIo5CLQvij4BAQgCJ?= =?us-ascii?q?oQTiH+LGgWTNZAcl02GGINch3aYQjcigU8yGggwgmeCUh2CBSOKAwEBAQ?= X-IronPort-AV: E=Sophos;i="5.45,504,1508817600"; d="scan'208";a="17300233" Original-Received: from 107-179-157-16.cpe.teksavvy.com (HELO pastel.home) ([107.179.157.16]) by smtp.teksavvy.com with ESMTP; 03 Jan 2018 17:45:27 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 9E4A060770; Wed, 3 Jan 2018 17:45:27 -0500 (EST) In-Reply-To: <20180103182917.GC5435@ACM> (Alan Mackenzie's message of "Wed, 3 Jan 2018 18:29:17 +0000") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 76.10.157.34 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:221565 Archived-At: > I agree. Frequently, I am looking for recent changes in a particular > function. C-s in the ChangeLog is much more convenient than a git blame > (or several of them in succession) followed by remembering the hash of an > indicated change (or several of them), followed by a git show (or several > of them). Hmm... could it be you haven't tried vc-region-history yet? Try: - put the region around the chunk of code of interest. - hit C-x v h (or M-x vc-region-history if you use Emacs<26). - enjoy pure bliss. > Let's please keep these individual function change descriptions in the VC > log (which will eventually become the ChangeLog). I tend to agree, but the text after the ":" should focus much more on the purpose of the change than on the description of the change itself. Stefan