From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH] Fix relative URI processing for gitsm
Date: Tue, 2 Oct 2018 17:08:02 -0400 [thread overview]
Message-ID: <20181002210803.189366-1-mark.hatle@windriver.com> (raw)
This patch depends on the prior patch set from Laurent Bonnans.
Identify and fix relative urls using os.path.join and os.path.realpath.
Mark Hatle (1):
gitsm: Allow relative URIs when fetching
lib/bb/fetch2/gitsm.py | 5 +++++
1 file changed, 5 insertions(+)
--
1.8.3.1
next reply other threads:[~2018-10-02 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 21:08 Mark Hatle [this message]
2018-10-02 21:08 ` [PATCH] gitsm: Allow relative URIs when fetching Mark Hatle
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=20181002210803.189366-1-mark.hatle@windriver.com \
--to=mark.hatle@windriver.com \
--cc=bitbake-devel@lists.openembedded.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: 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.