From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8239 invoked by alias); 21 Mar 2012 20:00:51 -0000 Received: (qmail 8223 invoked by uid 22791); 21 Mar 2012 20:00:50 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-mealy.atl.sa.earthlink.net (HELO elasmtp-mealy.atl.sa.earthlink.net) (209.86.89.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Mar 2012 20:00:37 +0000 Received: from [68.96.200.16] (helo=macbook2.local) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1SARi1-0004yu-91 for gdb@sourceware.org; Wed, 21 Mar 2012 16:00:37 -0400 Message-ID: <4F6A335D.6020401@earthlink.net> Date: Wed, 21 Mar 2012 20:00:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: gdb@sourceware.org Subject: Re: policy on splitting ChangeLogs? References: <201203192048.21988.vapier@gentoo.org> In-Reply-To: <201203192048.21988.vapier@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da9401967e904a6cd6bb5c12aa9615a12500c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00059.txt.bz2 On 3/19/12 5:48 PM, Mike Frysinger wrote: > i'd like to split up a ChangeLog to push arch-specific pieces into subdirs > rather than having the common ChangeLog be clogged with non-common changes. > is there a policy governing this ? or should i just cut all the relevant > pieces out of the common one and paste it into the subdir and be done ? > That's a decision left up to maintainers. In general, I've come to favor having fewer ChangeLog files, as with the ubiquity of public source-control systems, the manually-maintained logs are coming to seem more like an anachronism left over from pre-Internet days, and reducing the number is one way to spend less time and effort on managing them. Also, if you do per-arch logs, then you've forced everybody making a cross-arch change into editing dozens of ChangeLogs. So while as cross-platform types, we love to separate things into subdirs, I think this is one case where it will come to seem like more of a nuisance than a benefit. Stan