From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el) Date: Tue, 2 Jan 2018 00:06:11 -0800 Organization: UCLA Computer Science Department Message-ID: References: <87bmj6dda0.fsf@linux-m68k.org> <87vahe911g.fsf@lifelogs.com> <87374id7jy.fsf@linux-m68k.org> <877ett8g7k.fsf@lifelogs.com> <87a7yn7tqp.fsf@lifelogs.com> <878te75xa1.fsf@lifelogs.com> <87ind6l2tt.fsf@lifelogs.com> <877etklvsa.fsf@lifelogs.com> <83y3m0pv8u.fsf@gnu.org> <86608msw0h.fsf@dod.no> <838tdiet25.fsf@gnu.org> <87y3li4vh7.fsf@telefonica.net> <87efnan46u.fsf@linux-m68k.org> <86wp12qtgo.fsf@dod.no> <83tvw6chqv.fsf@gnu.org> <86shbprix7.fsf_-_@dod.no> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1514880310 27036 195.159.176.226 (2 Jan 2018 08:05:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 2 Jan 2018 08:05:10 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 Cc: emacs-devel@gnu.org To: rms@gnu.org, Steinar Bang Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 02 09:05:05 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 1eWHZG-0006Tn-9v for ged-emacs-devel@m.gmane.org; Tue, 02 Jan 2018 09:05:02 +0100 Original-Received: from localhost ([::1]:33859 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWHbD-00067w-CZ for ged-emacs-devel@m.gmane.org; Tue, 02 Jan 2018 03:07:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52872) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWHaU-00067k-Tb for emacs-devel@gnu.org; Tue, 02 Jan 2018 03:06:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWHaP-0000MY-Vk for emacs-devel@gnu.org; Tue, 02 Jan 2018 03:06:18 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:33024) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eWHaP-0000Lj-QL; Tue, 02 Jan 2018 03:06:13 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 293801613AF; Tue, 2 Jan 2018 00:06:12 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id od9eeC8j6q5T; Tue, 2 Jan 2018 00:06:11 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 682A9161436; Tue, 2 Jan 2018 00:06:11 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mGVByH01OrD0; Tue, 2 Jan 2018 00:06:11 -0800 (PST) Original-Received: from [192.168.1.9] (unknown [47.154.30.119]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 441121610A1; Tue, 2 Jan 2018 00:06:11 -0800 (PST) In-Reply-To: Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 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:221526 Archived-At: Richard Stallman wrote: > Was the whole history of our repository lost at that time ??? Not at all. It's still there. As part of maintenance I've done quite a bit of spelunking through the hi= story=20 of Emacs and other GNU programs, and the problem of following renames is = small=20 potatoes compared to the issues that normally consume most of my=20 software-archaeology time: namely, figuring out *why* a change was made, = not the=20 mechanical details of what changed. What would be most helpful (and I realize I'm asking for a lot) would be=20 ChangeLog entries or commit messages (it doesn't matter which) that expla= in the=20 *motivation* for each change. In contrast, often it is counterproductive = to=20 burden commit messages with mechanical details such as naming each and ev= ery=20 function that was modified, as it wastes developers' time to wade through= these=20 details when they're trying to look for stuff that's more important.