From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Switched from rsync to git, now emerge --sync fails
Date: Thu, 14 Oct 2021 09:22:22 +0100 [thread overview]
Message-ID: <5515605.DvuYhMxLoT@wstn> (raw)
In-Reply-To: <sk85uj$74e$1@ciao.gmane.io>
On Thursday, 14 October 2021 03:50:59 BST Grant Edwards wrote:
> On 2021-10-13, Rich Freeman <rich0@gentoo.org> wrote:
> > On Wed, Oct 13, 2021 at 2:50 PM Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> >> Is there some reason it should default
> >> to doing unlimited depth fetch operations?
> >
> > If all you want is a repo, no reason to set the depth higher.
>
> Then a default of 1 seems like the obvious "right" answer.
> Unfortunately, it defaults to "unlimited" according to
> https://wiki.gentoo.org/wiki//etc/portage/repos.conf
>
> sync-depth
>
> Specifies sync depth to use for DVCS repositories. If set to 0,
> the depth is unlimited. Defaults to 0.
>
> > If you want to see the history then you'll want it all.
>
> Apparently, that's the default. Without any sync-depth setting the
> fetch was stalling and then timing out after 60s. With sync-depth=1,
> the fetch completed in about 1s.
I have it set to 8 here, for no reason I can remember. Is there a disadvantage
in that?
--
Regards,
Peter.
next prev parent reply other threads:[~2021-10-14 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 18:25 [gentoo-user] Switched from rsync to git, now emerge --sync fails Grant Edwards
2021-10-13 18:37 ` Neil Bothwick
2021-10-13 18:50 ` [gentoo-user] " Grant Edwards
2021-10-13 19:35 ` Neil Bothwick
2021-10-13 20:11 ` Rich Freeman
2021-10-14 2:50 ` Grant Edwards
2021-10-14 8:22 ` Peter Humphrey [this message]
2021-10-14 8:28 ` Miles Malone
2021-10-14 9:52 ` Wol
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=5515605.DvuYhMxLoT@wstn \
--to=peter@prh.myzen.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