On Wed, 2019-06-19 at 11:37 +0900, Masahiro Yamada wrote:
On Wed, Jun 19, 2019 at 1:49 AM Wolfgang Denk wd@denx.de wrote:
Dear Bin,
In message 1560872253-6077-1-git-send-email-bmeng.cn@gmail.com you wrote:
Update all git repo links with the new gitlab ones.
Signed-off-by: Bin Meng bmeng.cn@gmail.com
MAINTAINERS | 106 ++++++++++++++++++++++++++++++------------------------------ 1 file changed, 53 insertions(+), 53 deletions(-)
Thanks a lot!
Acked-by: Wolfgang Denk wd@denx.de
Best regards,
Wolfgang Denk
This involves two changes [1] git.denx.de/* -> gitlab.denx.de/u-boot/* [2] git:// -> https://
Wolfgang said: " c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below. "
Which is efficient and better to advertise, git:// or https:// ? No difference in the clone speed?
Nothing is better than taking actual measurements. This is what I observe:
Benchmark #1: git clone git://gitlab.denx.de:60010/u-boot.git Time (mean ± σ): 35.970 s ± 3.251 s [User: 23.771 s, System: 3.932 s] Range (min … max): 32.600 s … 41.274 s 10 runs
Benchmark #2: git clone https://gitlab.denx.de/u-boot/u-boot.git Time (mean ± σ): 35.377 s ± 2.769 s [User: 24.838 s, System: 5.205 s] Range (min … max): 31.744 s … 39.598 s 10 runs
Summary 'git clone https://gitlab.denx.de/u-boot/u-boot.git' ran 1.02 ± 0.12 times faster than 'git clone git://gitlab.denx.de:60010/u-boot.git'
(Ignore the git:// URL, it was just temporary for testing)
As you can see, speed-wise there is next to no difference. BUT https is encrypted while git is not and https works better with proxy madness. So I would definitely choose https.