From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jon Beniston <jon@beniston.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't split executable paths with spaces in into multiple arguments
Date: Mon, 09 Nov 2009 18:04:00 -0000 [thread overview]
Message-ID: <m3k4xzinhw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091109174623.GR4557@adacore.com> (Joel Brobecker's message of "Mon, 9 Nov 2009 09:46:23 -0800")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> It seems to me that it would not be significantly harder for the code to
>> do the correct thing in all cases.
Joel> To be honest, I didn't even think about it, mostly because I thought
Joel> that the issue would be so rare that it was possibly just retorical.
Joel> So I felt that I shouldn't insist that we do the right thing in all
Joel> cases. Too lax?
Ordinarily my view is "forward biased": an improvement is an
improvement, and requiring perfection tends to raise the patch
submission bar too high.
In this particular case, though, I would probably have pushed back a
bit, first because the patch is already fixing a previous "can't happen"
assumption, and second because the correct code is really just 4 or 5
lines. (I thought for sure we would already have the quoting code lying
around, but I grepped a little and couldn't find it. It is odd that we
have buildargv to split the argv but nothing to quote it.)
Tom
next prev parent reply other threads:[~2009-11-09 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 13:26 Jon Beniston
2009-11-04 16:17 ` Joel Brobecker
2009-11-09 17:42 ` Tom Tromey
2009-11-09 17:46 ` Joel Brobecker
2009-11-09 18:04 ` Tom Tromey [this message]
2009-11-09 21:11 ` Joel Brobecker
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=m3k4xzinhw.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jon@beniston.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