This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFA: Remove gdb-events
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: tromey at redhat dot com
- Cc: stan at codesourcery dot com, gdb-patches at sources dot redhat dot com
- Date: Fri, 1 Aug 2008 19:37:27 +0200 (CEST)
- Subject: Re: RFA: Remove gdb-events
- References: <m3tzeubpw5.fsf@fleche.redhat.com> <487975AF.4030306@codesourcery.com> <m3abglbg8y.fsf@fleche.redhat.com> <m3ljzgzozh.fsf@fleche.redhat.com>
> X-Spam-Check-By: sourceware.org
> Cc: gdb-patches@sources.redhat.com
> From: Tom Tromey <tromey@redhat.com>
> Reply-To: Tom Tromey <tromey@redhat.com>
> Date: Fri, 01 Aug 2008 10:20:18 -0600
> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
> Sender: gdb-patches-owner@sourceware.org
> X-XS4ALL-DNSBL-Checked: mxdrop110.xs4all.nl checked 209.132.176.174 against DNS blacklists
> X-CNFS-Analysis: v=1.0 c=1 a=881O8E-6XdsA:10 a=2XsNsC2eOfWF1qdpl05llQ==:17
> a=qo2X1CjQWrMaJWK6xZoA:9 a=9A5clqTUE07V6g9w-5tw_btH0rQA:4
> a=jEp0ucaQiEUA:10 a=WcGY3-TIXCwA:10
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0.0 () none
> X-XS4ALL-Spam: NO
> Envelope-To: m.m.kettenis@xs4all.nl
> X-UIDL: 1217607658._smtp.mxdrop110.31168,S=3733
>
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>
> Tom> I'd like to propose changing this for gdb. I don't think merging is
> Tom> even needed. Folks can always look in subdir ChangeLog.old...
>
> Any comment on this?
>
> The concrete proposal is:
>
> * Rename gdb/doc/ChangeLog -> gdb/doc/ChangeLog.old
> * Rename gdb/testsuite/ChangeLog -> gdb/testsuite/ChangeLog.old
>
> ... and all future patches in these areas will just use gdb/ChangeLog.
>
> The rationale is that many patches span these directories, so keeping
> their ChangeLog entries together makes sense. On the flip side,
> keeping them separate does not seem to add much value -- it is just
> more work when preparing a patch.
While committing a testcase for bugs you fix is great, there is no
need to commit the testcase simultaniously with the fix. It is better
to actually commit the testcase as soon as the problem is known and
not wait until you have a fix.
Personally I like the fact that the testsuite Changelog is seperate.
It means I don't get distracted by testsuite changes when I'm looking
for code changes. And testsuite changes, which occur relatively
infrequent, don't get burried between lots of code changes.