From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] what's with the "\" in SSTATE_MIRRORS example in overview manual?
Date: Tue, 28 Sep 2021 10:14:50 +0200 [thread overview]
Message-ID: <20210928081450.6wuanw7mm76rb2tv@fedora> (raw)
In-Reply-To: <f7799882-d01c-de7b-be8a-45c2cf6e1eae@crashcourse.ca>
Hi Robert,
On Mon, Sep 27, 2021 at 01:45:53PM -0400, Robert P. J. Day wrote:
>
> from here:
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.yoctoproject.org_overview-2Dmanual_concepts.html-23shared-2Dstate-2Dcache&d=DwIBAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=iBMRw0D4E14V7Mp4p7EOj1bgXlIq0lFTp-9f5nnoGbk&s=g_KwAtXJ38EyzFMAmzfVCEUGZt8WjP4C8aTbr41h8aw&e=
>
> toward the end of that section, we see the example:
>
> SSTATE_MIRRORS ?= "\
> file://.\* https://urldefense.proofpoint.com/v2/url?u=http-3A__someserver.tld_share_sstate_PATH-3Bdownloadfilename-3DPATH&d=DwIBAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=iBMRw0D4E14V7Mp4p7EOj1bgXlIq0lFTp-9f5nnoGbk&s=ijxTmbCdCGt8GAHOyV_nDYONABR_e1JqCIC-b87jHNY&e= \n \
> file://.\* file:///some/local/dir/sstate/PATH"
> ^
>
> note those early backslashes in each line, which appear to totally
> break proper operation. it was only after i deleted that backslash
> that things worked.
>
> is this a recent change? did things used to work differently? those
> backslashes definitely seem incorrect. thoughts?
>
No this is an error made by the conversion script used to migrate from
XML to rST, please send a patch :)
Cheers,
Quentin
prev parent reply other threads:[~2021-09-28 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 17:45 what's with the "\" in SSTATE_MIRRORS example in overview manual? Robert P. J. Day
2021-09-28 8:14 ` Quentin Schulz [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=20210928081450.6wuanw7mm76rb2tv@fedora \
--to=quentin.schulz@theobroma-systems.com \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.