From: Antonio Ospite <ao2@ao2.it> To: qemu-devel@nongnu.org Cc: Antonio Ospite <antonio.ospite@collabora.com>, Antonio Ospite <ao2@ao2.it>, Peter Maydell <peter.maydell@linaro.org>, Eric Blake <eblake@redhat.com> Subject: [Qemu-devel] [PATCH v2 0/2] configure: disallow spaces and colons in source path and build path Date: Fri, 3 May 2019 10:27:26 +0200 [thread overview] Message-ID: <20190503082728.16485-1-ao2@ao2.it> (raw) Hi, Here is a v2 patch set to address https://bugs.launchpad.net/qemu/+bug/1817345 The series follows up to: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05290.html https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05573.html Changes since v1: - Add a preparatory patch to set source_path only once and in a more robust way. - Move the checks in configure after the source_path definition to avoid using realpath which is not available everywhere. - Cover also the build path in Makefile. An extensive explanation of why I think this is needed is here: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05398.html Thanks, Antonio Antonio Ospite (2): configure: set source_path only once and make its definition more robust configure: disallow spaces and colons in source path and build path Makefile | 4 ++++ configure | 12 +++++++++--- 2 files changed, 13 insertions(+), 3 deletions(-) -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
WARNING: multiple messages have this Message-ID (diff)
From: Antonio Ospite <ao2@ao2.it> To: qemu-devel@nongnu.org Cc: Peter Maydell <peter.maydell@linaro.org>, Antonio Ospite <ao2@ao2.it>, Antonio Ospite <antonio.ospite@collabora.com> Subject: [Qemu-devel] [PATCH v2 0/2] configure: disallow spaces and colons in source path and build path Date: Fri, 3 May 2019 10:27:26 +0200 [thread overview] Message-ID: <20190503082728.16485-1-ao2@ao2.it> (raw) Message-ID: <20190503082726.oUR0bJ_k_8l5WGAJgZg8zFloHiuD926nNoq3Xuq8Cjs@z> (raw) Hi, Here is a v2 patch set to address https://bugs.launchpad.net/qemu/+bug/1817345 The series follows up to: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05290.html https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05573.html Changes since v1: - Add a preparatory patch to set source_path only once and in a more robust way. - Move the checks in configure after the source_path definition to avoid using realpath which is not available everywhere. - Cover also the build path in Makefile. An extensive explanation of why I think this is needed is here: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05398.html Thanks, Antonio Antonio Ospite (2): configure: set source_path only once and make its definition more robust configure: disallow spaces and colons in source path and build path Makefile | 4 ++++ configure | 12 +++++++++--- 2 files changed, 13 insertions(+), 3 deletions(-) -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
next reply other threads:[~2019-05-03 8:27 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-03 8:27 Antonio Ospite [this message] 2019-05-03 8:27 ` [Qemu-devel] [PATCH v2 0/2] configure: disallow spaces and colons in source path and build path Antonio Ospite 2019-05-03 8:27 ` [Qemu-devel] [PATCH v2 1/2] configure: set source_path only once and make its definition more robust Antonio Ospite 2019-05-03 8:27 ` Antonio Ospite 2019-05-06 17:23 ` Eric Blake 2019-05-03 8:27 ` [Qemu-devel] [PATCH v2 2/2] configure: disallow spaces and colons in source path and build path Antonio Ospite 2019-05-03 8:27 ` Antonio Ospite 2019-05-06 17:27 ` Eric Blake 2019-05-06 20:23 ` Antonio Ospite 2019-05-09 14:42 ` Peter Maydell 2019-05-22 13:57 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier 2019-05-22 15:01 ` Antonio Ospite 2019-05-22 15:21 ` Laurent Vivier 2019-05-22 15:26 ` Antonio Ospite 2019-05-22 15:37 ` Laurent Vivier
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=20190503082728.16485-1-ao2@ao2.it \ --to=ao2@ao2.it \ --cc=antonio.ospite@collabora.com \ --cc=eblake@redhat.com \ --cc=peter.maydell@linaro.org \ --cc=qemu-devel@nongnu.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: linkBe 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 NNTP newsgroup(s).