From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: cp-names.c vs cp-namespace.c
Date: Wed, 11 May 2005 23:27:00 -0000 [thread overview]
Message-ID: <01c5567f$Blat.v2.4$f5312080@zahav.net.il> (raw)
In-Reply-To: <20050511200716.GA4104@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 11 May 2005 16:07:17 -0400)
> Date: Wed, 11 May 2005 16:07:17 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
>
> Couldn't you use a separate object directory on DOS, as IIRC we
> recommend everyone do?
That won't help in this case, since cp-names.o and cp-namespace.o will
also clash. Or did I misunderstood what you mean?
next prev parent reply other threads:[~2005-05-11 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 20:07 Eli Zaretskii
2005-05-11 20:08 ` Daniel Jacobowitz
2005-05-11 23:27 ` Eli Zaretskii [this message]
2005-05-11 23:32 ` Daniel Jacobowitz
2005-05-12 16:04 ` Daniel Jacobowitz
2005-05-12 16:20 ` Eli Zaretskii
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='01c5567f$Blat.v2.4$f5312080@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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