From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New portage git sync behavior
Date: Sun, 6 Nov 2016 13:20:35 -0800 [thread overview]
Message-ID: <41178b62-f9e8-b0a7-960a-378c2c443620@gentoo.org> (raw)
In-Reply-To: <CAJ0EP426qaw36dhW2BBjFQbYwKUaacz2W+jhAhuXbOKPBOA9og@mail.gmail.com>
On 09/20/2016 08:02 PM, Mike Gilbert wrote:
> Portage 2.3.1 changes the default behavior for git repositories to
> sync with a depth of 1. If you are using a development tree with
> emerge --sync, you may want to override this in repos.conf by setting
> sync-depth = 0.
>
> If you have accidentally converted your development tree into a
> shallow repository, you can undo the damage by running git fetch
> --unshallow.
>
I've proposed to revert the change in behavior because we've had too
many problems with it:
https://archives.gentoo.org/gentoo-portage-dev/message/e0314d5c748ec4098605c20d9b42b2a9
--
Thanks,
Zac
prev parent reply other threads:[~2016-11-06 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 3:02 [gentoo-dev] New portage git sync behavior Mike Gilbert
2016-10-12 18:45 ` konsolebox
2016-10-12 18:51 ` Mike Gilbert
2016-10-13 3:15 ` konsolebox
2016-10-13 13:42 ` Mike Gilbert
2016-10-13 1:36 ` Daniel Campbell
2016-10-13 3:14 ` konsolebox
2016-11-06 21:20 ` Zac Medico [this message]
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=41178b62-f9e8-b0a7-960a-378c2c443620@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@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