From: Michael Snyder <msnyder@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Berlin <dberlin@redhat.com>,
Michael Elizabeth Chastain <chastain@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] New C++ abstraction patch
Date: Wed, 21 Feb 2001 15:19:00 -0000 [thread overview]
Message-ID: <3A944CEB.2EDE2369@cygnus.com> (raw)
In-Reply-To: <3A9431C0.6E23A2E6@cygnus.com>
Andrew Cagney wrote:
>
> Daniel Berlin wrote:
>
> > I did this at first, but it seemed those only happened for certain
> > headers (something to do with $(SRCDIR)), so I undid it before
> > submitting the patch.
> > I'll redo it.
>
> Yep. What is happening is that no one can be bothered converting the
> entire file to that convention - automake will make the problem go away
> right :-). Instead things just get incrementally tweaked when a new
> file is added, broken include dependency gets noticed (or someone gets
> board).
Actually, I thought that the practice was only done selectively.
I don't see its usefulness, except for headers that might have
different names for different configurations.
next prev parent reply other threads:[~2001-02-21 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 17:35 Michael Elizabeth Chastain
2001-02-20 19:42 ` Daniel Berlin
2001-02-21 10:42 ` Andrew Cagney
2001-02-21 13:03 ` Daniel Berlin
2001-02-21 13:25 ` Andrew Cagney
2001-02-21 15:19 ` Michael Snyder [this message]
2001-02-22 8:14 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-02-21 7:43 Michael Elizabeth Chastain
2001-02-20 20:42 Michael Elizabeth Chastain
2001-02-20 23:42 ` Daniel Berlin
2001-02-21 11:53 ` Michael Snyder
2001-02-21 14:24 ` J.T. Conklin
2001-02-21 15:21 ` Michael Snyder
2001-02-20 16:02 Daniel Berlin
2001-02-21 1:53 ` Eli Zaretskii
2001-02-21 10:56 ` Andrew Cagney
2001-02-21 13:31 ` Daniel Berlin
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=3A944CEB.2EDE2369@cygnus.com \
--to=msnyder@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--cc=dberlin@redhat.com \
--cc=gdb-patches@sources.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