Opened on 01/28/19 at 12:19:27

Closed on 12/12/19 at 16:56:24

#3683 closed infra (wontfix)

Git clone via HTTPS does not give much interactive feedback

Reported by: Sebastian Huber Owned by:
Priority: normal Milestone: 5.1
Component: admin Version: 5
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

A Git clone via HTTPS does not give much interactive feedback. This could result in users thinking that a network issue exists and let them abort the command.

git clone https://git.rtems.org/rtems-libbsd
Cloning into 'rtems-libbsd'...
Checking out files: 100% (5159/5159), done.

vs.

git clone git://git.rtems.org/rtems-libbsd.git
Cloning into 'rtems-libbsd'...
remote: Counting objects: 34566, done.
remote: Compressing objects: 100% (8700/8700), done.
remote: Total 34566 (delta 24457), reused 34566 (delta 24457)
Receiving objects: 100% (34566/34566), 30.33 MiB | 1.34 MiB/s, done.                                                                                                                                                                                                           
Resolving deltas: 100% (24457/24457), done.                                                                                                                                                                                                                                    
Checking out files: 100% (5159/5159), done.

Change History (4)

comment:1 Changed on 01/28/19 at 12:35:07 by Sebastian Huber

Cloning the RSB via HTTPS doesn't work for me:

git clone https://git.rtems.org/rtems-source-builder rsb
Cloning into 'rsb'...

comment:2 Changed on 01/29/19 at 07:15:57 by Sebastian Huber

Ok, a git clone works via HTTPS, but it is extremely slow:

time git clone https://git.rtems.org/rtems-source-builder rsb
Cloning into 'rsb'...

real    6m41.242s
user    0m5.766s
sys     0m3.054s

time git clone git://git.rtems.org/rtems-source-builder.git rsb
Cloning into 'rsb'...
remote: Counting objects: 8758, done.
remote: Compressing objects: 100% (5222/5222), done.
remote: Total 8758 (delta 6078), reused 5028 (delta 3494)
Receiving objects: 100% (8758/8758), 2.89 MiB | 1.12 MiB/s, done.
Resolving deltas: 100% (6078/6078), done.

real    0m4.469s
user    0m0.415s
sys     0m0.083s

comment:3 Changed on 02/12/19 at 21:30:12 by Chris Johns

The https access has recently been discussed on the devel list. This thread is the start:

​https://lists.rtems.org/pipermail/devel/2019-February/024816.html

comment:4 Changed on 12/12/19 at 16:56:24 by Chris Johns

Resolution: → wontfix
Status: new → closed

I am going to close this ticket. The documentation uses git://.

If this is important funding is need to see why that we need to sort out in cgit.

Note: See TracTickets for help on using tickets.