Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: stan@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: Remove gdb-events
Date: Fri, 01 Aug 2008 17:40:00 -0000	[thread overview]
Message-ID: <200808011737.m71HbRm3029431@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <m3ljzgzozh.fsf@fleche.redhat.com> (message from Tom Tromey on 	Fri, 01 Aug 2008 10:20:18 -0600)

> 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.


  parent reply	other threads:[~2008-08-01 17:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13  0:16 Tom Tromey
2008-07-13  3:26 ` Stan Shebs
2008-07-13 21:56   ` Tom Tromey
2008-08-01 16:20     ` Tom Tromey
2008-08-01 16:33       ` Subdir ChangeLogs (was Re: RFA: Remove gdb-events) Stan Shebs
2008-08-01 17:10         ` Subdir ChangeLogs Tom Tromey
2008-08-01 17:27           ` Stan Shebs
2008-08-01 17:54             ` Tom Tromey
2008-08-01 18:44             ` Eli Zaretskii
2008-08-01 18:55               ` Tom Tromey
2008-08-01 19:25                 ` Eli Zaretskii
2008-08-01 19:33                   ` Tom Tromey
2008-08-01 20:11                     ` Thiago Jung Bauermann
2008-08-02  7:13                     ` Eli Zaretskii
2008-08-02 16:52                       ` Tom Tromey
2008-08-02 17:28                         ` Eli Zaretskii
2008-08-02 20:24                         ` Thiago Jung Bauermann
2008-08-03  0:02           ` Michael Snyder
2008-08-01 17:40       ` Mark Kettenis [this message]
2008-07-14 17:10 ` RFA: Remove gdb-events Joel Brobecker
2008-07-14 20:33   ` Tom Tromey
2008-07-15  6:54     ` Joel Brobecker
2008-07-17 23:41   ` Tom Tromey
2008-07-21 16:54     ` GDB/MI PING (was: "Re: RFA: Remove gdb-events") Joel Brobecker
2008-07-22  0:56     ` RFA: Remove gdb-events Tom Tromey
2008-07-25 16:11       ` Tom Tromey
2008-07-20 11:46 ` Eli Zaretskii
2008-07-21 17:13 ` Vladimir Prus
2008-07-22  0:32   ` Tom Tromey

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=200808011737.m71HbRm3029431@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=stan@codesourcery.com \
    --cc=tromey@redhat.com \
    /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