From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Excessive rsync time after git migration
Date: Sat, 15 Aug 2015 20:29:49 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.08.15.20.29.49@googlemail.com> (raw)
In-Reply-To: 55CF9311.1080102@gentoo.org
On Sat, 15 Aug 2015 15:29:21 -0400, Joshua Kinard wrote:
> This might already be covered in one of the other e-mail threads, but I've been
> super-busy as of late and just recently ran 'emerge --sync' on my main dev box
> for the first time after the git migration. I just synced my main dev box
> again, ~10 hours after the last sync, but it looks like the 'Manifest' files
> for *every* package in the tree are getting downloaded with each sync.
https://bugs.gentoo.org/show_bug.cgi?id=557192
-h
next prev parent reply other threads:[~2015-08-15 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 19:29 [gentoo-dev] Excessive rsync time after git migration Joshua Kinard
2015-08-15 20:16 ` Dale
2015-08-15 20:29 ` Holger Hoffstätte [this message]
2015-08-23 2:17 ` [gentoo-dev] " Philip Webb
2015-08-23 6:52 ` Michał Górny
2015-08-23 19:48 ` Gregory Woodbury
2015-08-23 20:02 ` Michał Górny
2015-08-23 20:04 ` Zac Medico
2015-08-23 20:43 ` Gregory Woodbury
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=pan.2015.08.15.20.29.49@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--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