From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: RefTeX Merge Date: Mon, 24 Sep 2012 14:13:03 +0800 Message-ID: <876274lzio.fsf@gnu.org> References: <877grkehl2.fsf@caeruleus.net> <505F574D.1050707@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348467200 4764 80.91.229.3 (24 Sep 2012 06:13:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2012 06:13:20 +0000 (UTC) Cc: Ralf Angeli , emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 24 08:13:25 2012 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 1TG1ux-0007it-CR for ged-emacs-devel@m.gmane.org; Mon, 24 Sep 2012 08:13:19 +0200 Original-Received: from localhost ([::1]:55348 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG1us-0007z6-Iq for ged-emacs-devel@m.gmane.org; Mon, 24 Sep 2012 02:13:14 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:54786) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG1up-0007xu-DY for emacs-devel@gnu.org; Mon, 24 Sep 2012 02:13:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TG1uo-0008DD-6e for emacs-devel@gnu.org; Mon, 24 Sep 2012 02:13:11 -0400 Original-Received: from mail-da0-f41.google.com ([209.85.210.41]:55559) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG1un-0008D8-Vz for emacs-devel@gnu.org; Mon, 24 Sep 2012 02:13:10 -0400 Original-Received: by dadi14 with SMTP id i14so134370dad.0 for ; Sun, 23 Sep 2012 23:13:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=10aHw4K9dMuHo8FkAlhDI1ItmuYVclTBEBZ55d1b7NY=; b=bky+qSubxZVUpkS/kZ97FJQFteUoHJBTvQl6ahkjj25UGMfD/m0LkNQp7bDDipPSCW 73k22l6MoeFygNoDs08RlaD1UFv+2WoQBtHE2mGM7NhIy4IJvcRkdqPjM3avC3w8YCFE m2U9m+5NFypyKvZxCpKAXylikm0Vkoq9BFU3Q0aVM/NfCHS5H+GR1I7HT7CvDyN0YTK6 XbLGjreV4qjUZdcfs0erQx9h20rb18dKXDdtXOOKC/0s84fyj+jlg0azQya9PaY5t8WW nraS16E5A+zCHXcyjatFX0G928lk3Bthcsn0e6EvPHN7947YC7cVXr6MRSqA9XUVSqsC 4zlA== Original-Received: by 10.68.242.231 with SMTP id wt7mr33758629pbc.99.1348467189193; Sun, 23 Sep 2012 23:13:09 -0700 (PDT) Original-Received: from ulysses ([155.69.17.99]) by mx.google.com with ESMTPS id y11sm9129462pbv.66.2012.09.23.23.13.05 (version=SSLv3 cipher=OTHER); Sun, 23 Sep 2012 23:13:08 -0700 (PDT) In-Reply-To: <505F574D.1050707@cs.ucla.edu> (Paul Eggert's message of "Sun, 23 Sep 2012 11:39:09 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.210.41 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:153504 Archived-At: Paul Eggert writes: > One possibility is to create a new directory > lisp/textmodes/reftex, move the RefTeX source there, > and create a ChangeLog there, starting the ChangeLog with all the > old history followed by a note saying what happened. No. Since reftex.el is one file, it is not worth creating a subdirectory just for it. When a file is synched to the Emacs repository, the ChangeLog typically only describes the differences relative to the previous version. That's usually a truncated version of the file's full ChangeLog history, but in practice this hasn't been a big problem. Adding a big mass of ChangeLog entries is not very helpful for people browsing the Emacs ChangeLog. How large are the ChangeLog entries in question? Putting them in the commit log may be a fine solution. (Normally, one would use bzr join to preserve the history, but bzr join seems to be badly broken.)