From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v2] x86: Remove libopcodes dependency
Date: Fri, 2 Dec 2022 08:10:33 +0100 [thread overview]
Message-ID: <a66922a0-3902-8c52-eaa8-c3fe1b954ecc@suse.com> (raw)
In-Reply-To: <CAMe9rOqvytNg2yKKycF0iVcMghDZ0ER2g2pifRaO3=mc_48tQg@mail.gmail.com>
On 01.12.2022 19:20, H.J. Lu wrote:
> It looks like
>
> # foo \
> bar
>
> 2 lines are treated as a single line.
Hmm, I didn't think this was the case on all make versions supported
(iirc there's not even a minimum version stated anywhere, which quite
possibly is a mistake), but looking at even the oldest numbered
version in their repo (3.70.2) this has been documented behavior
already then. I'm puzzled in particular because quite recently I saw
a change specifically dealing with the supposed behavior (which I
didn't question because it was matching my recollection). I'm sorry
for the noise here.
Jan
prev parent reply other threads:[~2022-12-02 7:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 18:19 [PATCH] " H.J. Lu
2022-11-23 8:36 ` Jan Beulich
2022-11-28 23:43 ` H.J. Lu
2022-11-29 9:12 ` Jan Beulich
2022-11-24 10:19 ` Jan Beulich
2022-11-28 23:49 ` [PATCH v2] " H.J. Lu
2022-11-29 9:22 ` Jan Beulich
2022-11-29 19:38 ` H.J. Lu
2022-11-30 0:06 ` H.J. Lu
2022-11-30 6:58 ` Jan Beulich
2022-11-30 22:22 ` H.J. Lu
2022-12-01 7:41 ` Jan Beulich
2022-12-01 18:26 ` [PATCH v3] " H.J. Lu
2022-12-02 7:16 ` Jan Beulich
2022-12-02 17:19 ` H.J. Lu
2022-12-05 11:25 ` Jan Beulich
2022-11-30 7:31 ` [PATCH v2] " Jan Beulich
2022-11-30 22:15 ` H.J. Lu
2022-12-01 7:21 ` Jan Beulich
2022-12-01 18:20 ` H.J. Lu
2022-12-02 7:10 ` Jan Beulich [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=a66922a0-3902-8c52-eaa8-c3fe1b954ecc@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).