public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Clément Chigot" <chigot@adacore.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] windres: add quotes around preprocessor cmd if needed
Date: Tue, 28 Jun 2022 12:16:49 +0200	[thread overview]
Message-ID: <10734bc9-6686-0426-c2c8-9dc8173392fe@suse.com> (raw)
In-Reply-To: <CAJ307EgYEyJvpegZBS2nsSBuFRbmiTMYrSno-+jwRtgmT+um_A@mail.gmail.com>

On 28.06.2022 11:37, Clément Chigot wrote:
> On Tue, Jun 28, 2022 at 11:00 AM Jan Beulich <jbeulich@suse.com> wrote:
>>
>> On 28.06.2022 09:35, Clément Chigot via Binutils wrote:
>>> This patch ensures that the gcc binary called by windres is quoted if
>>> needed. Otherwise, errors can occur if the gcc is under a folder having
>>> a name containing a space (eg "Program Files").
>>>
>>> binutils/
>>>         * resrc.c (DEFAULT_PREPROCESSOR): Split into...
>>>         (DEFAULT_PREPROCESSOR_CMD): that...
>>>         (DEFAULT_PREPROCESSOR_ARGS): and that.
>>>         (look_for_default): Add quotes around the command if needed.
>>>         (read_rc_file): Adapt to new defines.
>>
>> Commenting is a little difficult without you providing the patch (also)
>> inline:
> 
> IIRC, it should be done directly but the "é" in my name makes the
> mailservers think my patches are binaries...

I don't think that's what is the issue. There may be mail clients which
display text attachments, but then it's still an attachment, and other
clients may only ever handle attachments as such (mine, for example,
might display such an attachment, but would not consider it part of the
reply context when first setting up a reply mail, yet having it there
is what is the primary goal when talking about commenting on patches).
If you can't configure your client such that inlined patches make it
through ungarbled, it would still be helpful if you could _also_ inline
the patch, indicating that it may not be well-formed and hence for
applying the attached variant should be used.

Jan

  reply	other threads:[~2022-06-28 10:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  7:35 Clément Chigot
2022-06-28  9:00 ` Jan Beulich
2022-06-28  9:37   ` Clément Chigot
2022-06-28 10:16     ` Jan Beulich [this message]
2022-06-28 11:57       ` Clément Chigot
2022-06-28 12:26     ` Clément Chigot
2022-06-28 13:51       ` Jan Beulich
2022-06-28 14:18         ` Clément Chigot
2022-06-28 14:40           ` Jan Beulich
2022-06-28 14:55             ` Clément Chigot

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=10734bc9-6686-0426-c2c8-9dc8173392fe@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=chigot@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).