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) Date: Fri, 12 Jan 2018 18:33:32 -0800 Organization: UCLA Computer Science Department Message-ID: References: <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> <7c7503b4-1f82-8a25-fedd-c61c3e7629f6@cs.ucla.edu> <83zi5o6w4p.fsf@gnu.org> <745d2f02-8ca3-8962-0de4-053340c8fa63@cs.ucla.edu> <83efmx6862.fsf@gnu.org> <83wp0n32se.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1515810765 4253 195.159.176.226 (13 Jan 2018 02:32:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 13 Jan 2018 02:32:45 +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: Eli Zaretskii , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 13 03:32:40 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 1eaBcZ-0000Pm-0w for ged-emacs-devel@m.gmane.org; Sat, 13 Jan 2018 03:32:35 +0100 Original-Received: from localhost ([::1]:58414 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eaBeY-0002pH-PO for ged-emacs-devel@m.gmane.org; Fri, 12 Jan 2018 21:34:38 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52705) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eaBdb-0002nt-TI for emacs-devel@gnu.org; Fri, 12 Jan 2018 21:33:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eaBdb-0000sn-4g for emacs-devel@gnu.org; Fri, 12 Jan 2018 21:33:39 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:44042) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eaBdX-0000n4-D7; Fri, 12 Jan 2018 21:33:35 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 7E3B41616AC; Fri, 12 Jan 2018 18:33:33 -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 ylPOGGCV3Wu2; Fri, 12 Jan 2018 18:33:32 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 99E061616B0; Fri, 12 Jan 2018 18:33:32 -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 yvkaGAMEvbg5; Fri, 12 Jan 2018 18:33:32 -0800 (PST) Original-Received: from [192.168.1.9] (unknown [47.154.30.119]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 7479E1616AC; Fri, 12 Jan 2018 18:33:32 -0800 (PST) In-Reply-To: <83wp0n32se.fsf@gnu.org> 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:221907 Archived-At: Eli Zaretskii wrote: >> It's perfectly OK for someone to decide to hack on Emacs starting from >> a tarball rather than from a Git tree, but then this user gets what he >> asked for. > Since I'm frequently in that situation, How so? I'm almost never in that situation. Do you download distribution tarballs and hack on them directly? If not, how do you end up with development copies of Emacs without having a repository near to hand? > keeping the ChangeLog files > nowadays means a barely tangible effort from the project. We're not talking about removing the existing ChangeLog files. We're talking about what should be put into commit messages from here on out. That is an ongoing and nontrivial maintenance effort, and if we can ease the burden of writing commit messages then that will be a win.