Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Stan Shebs <stanshebs@earthlink.net>
Subject: Re: policy on splitting ChangeLogs?
Date: Fri, 23 Mar 2012 03:25:00 -0000	[thread overview]
Message-ID: <201203222325.26066.vapier@gentoo.org> (raw)
In-Reply-To: <4F6A335D.6020401@earthlink.net>

[-- Attachment #1: Type: Text/Plain, Size: 1362 bytes --]

On Wednesday 21 March 2012 16:00:29 Stan Shebs wrote:
> 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.

in the case of sim tests, i don't think so.  it's uncommon to get updates that 
span multiple arches in there when compared to the number of arch-specific 
entries.  i think i saw one or two that spanned multiple dirs during the 
split.  certainly YMMV.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-03-23  3:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  0:48 Mike Frysinger
2012-03-21  2:19 ` Doug Evans
2012-03-21  2:26   ` Mike Frysinger
2012-03-21  2:42     ` Doug Evans
2012-03-21 20:00 ` Stan Shebs
2012-03-23  3:25   ` Mike Frysinger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201203222325.26066.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox