From: Deborah Brouwer <deborah.brouwer@collabora.com>
To: hverkuil-cisco@xs4all.nl
Cc: linux-media@vger.kernel.org
Subject: build scripts: branches with forward slashes in names
Date: Thu, 23 Nov 2023 14:22:49 -0800 [thread overview]
Message-ID: <ZV_QuX5YScktbQi3@mz550> (raw)
Hi Hans,
Have you ever had a problem running the build scripts on branches with
forward slashes in their names?
So, for example, I add my repo to env.sh
myrepo=https://gitlab.collabora.com/chipsnmedia/kernel
I run ./build.sh setup and I can see it fetching my repo and including
my branch "dbrouwer/KConfig_fix", but if try to run:
./build.sh -test all dbrouwer/KConfig_fix
I get this error:
"fatal: 'dbrouwer/KConfig_fix' is not a commit and a branch 'build-test' cannot be created from it"
But then if I change the branch name to remove the forward slash "KConfig_fix" it works fine again.
Have you noticed anything similar? Could it be easily fixed?
Thanks,
Deborah
next reply other threads:[~2023-11-23 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 22:22 Deborah Brouwer [this message]
2023-11-24 7:23 ` build scripts: branches with forward slashes in names Hans Verkuil
2023-11-24 9:37 ` Hans Verkuil
2023-11-24 18:00 ` Deborah Brouwer
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=ZV_QuX5YScktbQi3@mz550 \
--to=deborah.brouwer@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox