From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] scripts/build-many-glibcs.py: Use https:// for sourceware.org Git clones
Date: Tue, 30 Aug 2022 06:00:33 +0200 [thread overview]
Message-ID: <871qsy753y.fsf@oldenburg.str.redhat.com> (raw)
Tested by running a checkout with these changes. No observed speed
difference; sourceware.org nowadays implements the Git protocol over
https://.
---
scripts/build-many-glibcs.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 98f02104a2..283e6fe738 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -854,7 +854,7 @@ class Context(object):
"""Check out the given version of the given component from version
control. Return a revision identifier."""
if component == 'binutils':
- git_url = 'git://sourceware.org/git/binutils-gdb.git'
+ git_url = 'https://sourceware.org/git/binutils-gdb.git'
if version == 'mainline':
git_branch = 'master'
else:
@@ -868,7 +868,7 @@ class Context(object):
branch = 'releases/gcc-%s' % version
return self.gcc_checkout(branch, update)
elif component == 'glibc':
- git_url = 'git://sourceware.org/git/glibc.git'
+ git_url = 'https://sourceware.org/git/glibc.git'
if version == 'mainline':
git_branch = 'master'
else:
@@ -957,7 +957,7 @@ class Context(object):
shutil.rmtree(self.component_srcdir('gcc'))
update = False
if not update:
- self.git_checkout('gcc', 'git://gcc.gnu.org/git/gcc.git',
+ self.git_checkout('gcc', 'https://gcc.gnu.org/git/gcc.git',
branch, update)
subprocess.run(['contrib/gcc_update', '--silent'],
cwd=self.component_srcdir('gcc'), check=True)
base-commit: d0e357ff45a75553dee3b17ed7d303bfa544f6fe
next reply other threads:[~2022-08-30 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:00 Florian Weimer [this message]
2022-09-05 13:33 ` Adhemerval Zanella Netto
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=871qsy753y.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).