From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Daniel Jacobowitz <drow@mvista.com>,
gdb-patches@sources.redhat.com, mec@shout.net
Subject: Re: [rfa/c++testsuite] (was Re: patch for PR gdb/574)
Date: Fri, 27 Sep 2002 16:42:00 -0000 [thread overview]
Message-ID: <3D94ECDB.3080908@redhat.com> (raw)
In-Reply-To: <ro14rcbko0u.fsf@jackfruit.Stanford.EDU>
> On Fri, 27 Sep 2002 19:20:14 -0400, Andrew Cagney <ac131313@redhat.com> said:
>
>
>>> 2002-08-22 David Carlton <carlton@math.stanford.edu>
>>> * gdb.c++/pr-574.exp: New file.
>
>
>>> * gdb.c++/pr-574.cc: New file.
>>>
>
>
>> Suggest a rename to c++/gdb574.*. MI's using that and got in just a
>> tiny bit earlier :-)
>
>
> Grump, grump, grump. Being a lazy person, I will give the following
> justification for my naming scheme: you're proposing to change the PR
> naming category so that that PR would turn into c++574. (Or do
> existing closed PR's not get moved?) So it would make more sense to
> call it gdb.c++/c++574.cc, which sounds silly: the whole directory is
> about C++! And gdb.c++/gdb574.cc is only a little less silly, or
> arguably even sillier: every single file in that directory, in its
> parent, and in the parent of its parent is about GDB, so putting 'gdb'
> in the name of a file is just plain old redundant. Whereas putting
> 'pr' in the name of a file isn't redundant at all.
Arh, the `gdb' is to disguinguish it from gcc, not from other sub
categories :-)
Andrew
prev parent reply other threads:[~2002-09-27 23:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 12:02 patch for PR gdb/574 david carlton
2002-07-22 12:16 ` Daniel Jacobowitz
2002-07-22 12:18 ` david carlton
2002-07-23 16:47 ` Jim Blandy
2002-08-15 20:26 ` Daniel Jacobowitz
2002-08-15 20:48 ` David Carlton
2002-08-16 16:10 ` [rfa/c++testsuite] (was Re: patch for PR gdb/574) David Carlton
2002-08-22 10:10 ` David Carlton
2002-09-27 16:20 ` Andrew Cagney
2002-09-27 16:32 ` David Carlton
2002-09-27 16:42 ` Andrew Cagney [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=3D94ECDB.3080908@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.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