From: Peter Korsgaard <peter@korsgaard.com>
To: ckhardin@gmail.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/scripts: handle paths with regex characters in per-package
Date: Tue, 07 Jun 2022 16:03:52 +0200 [thread overview]
Message-ID: <87r1406053.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220604032345.89818-1-ckhardin@gmail.com> (ckhardin@gmail.com's message of "Fri, 3 Jun 2022 20:23:45 -0700")
>>>>> "ckhardin" == ckhardin <ckhardin@gmail.com> writes:
> From: Charles Hardin <ckhardin@gmail.com>
> Some constraints on a setup ended up with a plus sign in the path
> for historical reasons and would then fail to match on the comparison
> of the host/lib dir match. So, the =~ for bash can be augmented
> with a double quote expansion to preserve the literal value of
> the characters in the variable.
> Example Path: /home/vagrant/test+buildroot/per-package
> Signed-off-by: Charles Hardin <ckhardin@gmail.com>
Committed to 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-06-07 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 3:23 [Buildroot] [PATCH 1/1] support/scripts: handle paths with regex characters in per-package ckhardin
2022-06-04 7:56 ` Yann E. MORIN
2022-06-07 14:03 ` Peter Korsgaard [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=87r1406053.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ckhardin@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