public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --sync
Date: Mon, 1 Aug 2022 08:22:11 +0100	[thread overview]
Message-ID: <20220801082150.1eac4fb2@digimed.co.uk> (raw)
In-Reply-To: <4759200.31r3eYUQgx@lenovo.localdomain>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

On Mon, 01 Aug 2022 07:58:05 +0100, Michael wrote:

> 1. It used to be the case the first time you run git it would try to
> download GB of commits history and take ages to do so on a slow
> connection.  The solution used to be to add "EGIT_CLONE_TYPE=shallow"
> in your make.conf, but I'm not sure if this is still needed (I don't
> use git).

It doesn't seem to be the case, running sync with an empty portage tree
gives

>>> Syncing repository 'gentoo' into '/var/portage'...
/usr/bin/git clone --depth 1 https://github.com/gentoo-mirror/gentoo .

% du /var/portage
608M    /var/portage

It did take 32s, but most of that was the Performing Global Updates stage.


-- 
Neil Bothwick

"A hundred years of forgetting and it all comes rushing back..."

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-08-01  7:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 19:51 [gentoo-user] --sync n952162
2022-07-31 20:24 ` Jack
2022-07-31 20:32 ` Dale
2022-07-31 20:43 ` Neil Bothwick
2022-07-31 23:49   ` Peter Humphrey
2022-08-01  0:21     ` Lee
2022-08-02 16:28   ` [ME TOO] " Dr Rainer Woitok
2022-07-31 20:53 ` Stefan Schmiedl
2022-07-31 22:55   ` Lee
2022-07-31 23:21     ` Neil Bothwick
2022-08-01  5:09 ` n952162
2022-08-01  6:58   ` Michael
2022-08-01  7:22     ` Neil Bothwick [this message]
2022-08-01  9:43     ` tastytea
2022-08-01 10:08       ` Michael
2022-08-02 13:22 ` [gentoo-user] --sync Grant Edwards

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=20220801082150.1eac4fb2@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.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