From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fate: allow https for git URLs
Date: Wed, 24 Apr 2024 23:28:11 +0200
Message-ID: <439620ac-f50f-4c2f-b272-e158a228fb5d@rothenpieler.org> (raw)
In-Reply-To: <ZilxX4YyCGugsZN-@metallschleimette>
On 24.04.2024 22:53, Alexander Strasser via ffmpeg-devel wrote:
> On 2024-04-24 22:26 +0200, Timo Rothenpieler wrote:
>> On 24.04.2024 22:12, Alexander Strasser via ffmpeg-devel wrote:
>>> On 2024-04-24 22:01 +0200, Timo Rothenpieler wrote:
>>>> ---
>>>> tests/fate.sh | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/tests/fate.sh b/tests/fate.sh
>>>> index c5ee18de80..4081e865ae 100755
>>>> --- a/tests/fate.sh
>>>> +++ b/tests/fate.sh
>>>> @@ -30,14 +30,14 @@ lock(){
>>>> checkout(){
>>>> case "$repo" in
>>>> file:*|/*) src="${repo#file:}" ;;
>>>> - git:*) git clone --quiet --branch "$branch" "$repo" "$src" ;;
>>>> + git:*|https:*) git clone --quiet --branch "$branch" "$repo" "$src" ;;
>>>> esac
>>>> }
>>>>
>>>> update()(
>>>> cd ${src} || return
>>>> case "$repo" in
>>>> - git:*) git fetch --quiet --force && git reset --quiet --hard "origin/$branch" ;;
>>>> + git:*|https:*) git fetch --quiet --force && git reset --quiet --hard "origin/$branch" ;;
>>>> esac
>>>> )
>>>
>>
>> If you manually clone the repo, you can use whatever you like anyway, since
>
> Sorry my initial wording was probably ambiguous.
>
> I meant in the repo variable in a fate_config.sh
>
>
>> it never actually uses the URL for anything after the initial clone.
>
> The URL isn't used per se, but it's used to decide whether to
> git fetch or not inside the call to update, isn't it?
>
Yeah, that's pretty much the only thing it's used for.
I also considered to turn the check around, and always assume it's a
valid git URL unless the file: thingy is recognized.
That way ssh URLs and cloning from local paths would become possible.
But that runs a higher risk of breaking someones setup.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-04-24 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 20:01 Timo Rothenpieler
2024-04-24 20:12 ` Alexander Strasser via ffmpeg-devel
2024-04-24 20:26 ` Timo Rothenpieler
2024-04-24 20:53 ` Alexander Strasser via ffmpeg-devel
2024-04-24 21:28 ` Timo Rothenpieler [this message]
2024-04-27 21:31 ` Timo Rothenpieler
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=439620ac-f50f-4c2f-b272-e158a228fb5d@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git