Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@earthlink.net>
To: Tom Tromey <tromey@redhat.com>
Cc: Stan Shebs <stan@codesourcery.com>, gdb-patches@sources.redhat.com
Subject: Re: Subdir ChangeLogs
Date: Fri, 01 Aug 2008 17:27:00 -0000	[thread overview]
Message-ID: <4893474C.3000103@earthlink.net> (raw)
In-Reply-To: <m3hca4zmo9.fsf@fleche.redhat.com>

Tom Tromey wrote:
>>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
>>>>>>             
>
> Tom> Any comment on this?
>
> Stan> I thought I did...
>
> Oops, sorry Stan.
>
> Tom> The concrete proposal is:
> Tom> * Rename gdb/doc/ChangeLog -> gdb/doc/ChangeLog.old
>
> Stan> Yes.
>
> Is that an official ok?  Or just agreement?
>   
Since it affects everybody's workflow, I'd like to see at least one more 
opinion. Let's give it until the end of Monday, if nobody else responds, 
then let's just go ahead and do it.
> Tom> * Rename gdb/testsuite/ChangeLog -> gdb/testsuite/ChangeLog.old
>
> Stan> I don't like this idea so much. Partly because testsuite is a whole
> Stan> complex of subdirs, partly because I still think of testsuite as a
> Stan> separate "product" even though it hasn't been packaged separately in
> Stan> years, but basically a non-rational reaction. But if everybody else
> Stan> wants this, that's fine.
>
> If it helps any, Classpath has many more directories than
> gdb/testsuite, and a single ChangeLog works just fine there.  It is
> actually clearer this way, IMO, since related changes are grouped
> together.
>   
I know I know, that's the rational viewpoint. :-) It does seem that most 
of src/ and gcc/ continues to have separate testsuite ChangeLogs, is 
that due to resistance or simply inertia?

Stan


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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13  0:16 RFA: Remove gdb-events 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 [this message]
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       ` RFA: Remove gdb-events Mark Kettenis
2008-07-14 17:10 ` 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=4893474C.3000103@earthlink.net \
    --to=stanshebs@earthlink.net \
    --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