From: Mark Mitchell <mark@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: PowerPC simulator doesn't handle spaces in filenames
Date: Thu, 02 Feb 2006 06:50:00 -0000 [thread overview]
Message-ID: <43E1ABA4.9050806@codesourcery.com> (raw)
In-Reply-To: <20060202014431.GA19694@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Tue, Jan 24, 2006 at 10:23:16PM -0800, Mark Mitchell wrote:
>
>>2006-01-24 Mark Mitchell <mark@codesourcery.com>
>>
>> * emul_netbsd.c (emul_netbsd_create): Quote file-name property.
>> * emul_unix.c (emul_unix_create): Likewise.
>> * tree.c (libiberty.h): Include it.
>> (tree_quote_property): New function.
>> * tree.h (tree_quote_property): Declare.
>
>
> Yes, this is fine. Thanks.
Committed, thanks!
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
prev parent reply other threads:[~2006-02-02 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 5:59 Mark Mitchell
2006-01-24 21:24 ` Daniel Jacobowitz
2006-01-25 6:23 ` Mark Mitchell
2006-02-02 1:44 ` Daniel Jacobowitz
2006-02-02 6:50 ` Mark Mitchell [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=43E1ABA4.9050806@codesourcery.com \
--to=mark@codesourcery.com \
--cc=drow@false.org \
--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