Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Apr 2023 06:12:18 +0000
From:      "Piotr P. Stefaniak" <pstef@freebsd.org>
To:        Colin Percival <cperciva@freebsd.org>
Cc:        src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org
Subject:   Re: git: df53ae0fdd98 - main - Remove portsnap(8)
Message-ID:  <ZETMQtuwit%2Bc/0MW@freefall.freebsd.org>
In-Reply-To: <202304230112.33N1ChPx076100@gitrepo.freebsd.org>
References:  <202304230112.33N1ChPx076100@gitrepo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-04-23 01:12:43, Colin Percival wrote:
>    Remove portsnap(8)
>
>    Rather than having a tool in the FreeBSD base system for obtaining
>    the FreeBSD ports tree, users are encouraged to `pkg install git`
>    and then `git clone https://git.FreeBSD.org/ports.git /usr/ports`.

With my 64 KB/s downlink a shallow copy of just the main branch takes
almost 4 hours. What's worse, git has no way of resuming an interrupted
download. I don't remember if gitup is better in that regard.

What I usually do with repos like this is I clone it from a well
connected remote machine, archive just the .git directory, copy that
using rsync or sftp and finally do `git reset --hard`.

It would be nice to be able to just rsync worktrees of our repositories
from a public source.

Piotr



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZETMQtuwit%2Bc/0MW>