From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: Renaming NEWS Date: Tue, 22 May 2007 16:12:01 +0900 Message-ID: References: <17989.37070.393150.565546@kahikatea.snap.net.nz> <17994.32856.216525.50726@kahikatea.snap.net.nz> <17994.54868.931947.611990@kahikatea.snap.net.nz> <17995.31640.399794.621018@kahikatea.snap.net.nz> <17995.53754.860573.633945@kahikatea.snap.net.nz> <17996.55425.495501.592760@kahikatea.snap.net.nz> <17998.5626.348375.91578@kahikatea.snap.net.nz> <17998.45589.625578.730270@kahikatea.snap.net.nz> <17999.58366.589991.627229@kahikatea.snap.net.nz> <0l8xbjgsq4.fsf_-_@fencepost.gnu.org> <87iran41xo.fsf@catnip.gol.com> <86veemk1o5.fsf@lola.quinscape.zz> <40646l9wzy.fsf@fencepost.gnu.org> Reply-To: Miles Bader NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1179817947 25822 80.91.229.12 (22 May 2007 07:12:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 22 May 2007 07:12:27 +0000 (UTC) Cc: Eli Zaretskii , Nick Roberts , emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 22 09:12:25 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HqOXg-0003hm-6k for ged-emacs-devel@m.gmane.org; Tue, 22 May 2007 09:12:24 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HqOXf-0004eB-Iv for ged-emacs-devel@m.gmane.org; Tue, 22 May 2007 03:12:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HqOXb-0004Zr-1z for emacs-devel@gnu.org; Tue, 22 May 2007 03:12:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HqOXZ-0004Xm-EG for emacs-devel@gnu.org; Tue, 22 May 2007 03:12:18 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HqOXZ-0004Xj-9g for emacs-devel@gnu.org; Tue, 22 May 2007 03:12:17 -0400 Original-Received: from tyo201.gate.nec.co.jp ([202.32.8.193]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HqOXN-0003Rx-Iv; Tue, 22 May 2007 03:12:06 -0400 Original-Received: from relay11.aps.necel.com ([10.29.19.46]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l4M7C3Rn010752; Tue, 22 May 2007 16:12:03 +0900 (JST) Original-Received: from relay31.aps.necel.com ([10.29.19.20] [10.29.19.20]) by relay11.aps.necel.com with ESMTP; Tue, 22 May 2007 16:12:02 +0900 Original-Received: from dhapc248.dev.necel.com ([10.114.97.235] [10.114.97.235]) by relay31.aps.necel.com with ESMTP; Tue, 22 May 2007 16:12:02 +0900 Original-Received: by dhapc248.dev.necel.com (Postfix, from userid 31295) id 37CB94D5; Tue, 22 May 2007 16:12:02 +0900 (JST) System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: <40646l9wzy.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue\, 22 May 2007 02\:46\:09 -0400") Original-Lines: 31 X-detected-kernel: Solaris 8 (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:71579 Archived-At: Glenn Morris writes: > No, leaving the arch tag in lisp/ChangeLog would seem to make more > sense to me. Anyone who is using this tag must expect it to refer to > the "current lisp ChangeLog", not some random ChangeLog.NN. > ChangeLog.12, which will almost never be used, should get a new arch > tag. People don't use the tag. The tag is used by tools to establish file identity. In general the tag should move with the file (and will be used by arch to move the file in a branch when merging into the branch). If you want "ChangeLog" changes on the branch to continue to go to the "ChangeLog" on the trunk then indeed, you're right ... but this will complicate things to some degree with merging to other branches, because the "contents move" on the trunk will be essentially be a huge delete from one file (ChangeLog) and a huge add to another file (ChangeLog.12) -- and large textual changes like that are quite brittle (e.g., the presence of slight text differences in the ChangeLog of another branch will cause a merge conflict for the whole huge chunk). I guess it doesn't matter too much one way or another though; since it's a rare event and affects few files, it's not really a big deal to fix things up by hand. -Miles -- "I distrust a research person who is always obviously busy on a task." --Robert Frosch, VP, GM Research