From: Ricardo Correia <gentoo-dev@wizy.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Proposal for an alternative portage tree sync method
Date: Wed, 23 Mar 2005 22:49:47 +0000 [thread overview]
Message-ID: <200503232249.47445.gentoo-dev@wizy.org> (raw)
In-Reply-To: <20050324101350.CC09.NICK@rout.co.nz>
On Wednesday 23 March 2005 22:15, Nick Rout wrote:
> You may need to get a few friends to do it over the net too, in order to
> try it on something less traffic friendly than your LAN.
>
In fact, with the help of some people we already tried it on a server with a 1
Mbps upstream and are about to setup one with 100Mbps, for more general use.
The results of some tests are already in the forum post.
For now, it seems that it takes more bandwidth than rsync, much it's a great
improvement over emerge-webrsync.
However, we are also considering some possible improvements in the process.
Personally, I'd be happy if people use it instead of emerge-webrsync.
I can't use rsync, so I know I will ;)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-23 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 7:15 [gentoo-dev] Proposal for an alternative portage tree sync method Ricardo Correia
2005-03-22 12:45 ` Daniel Drake
2005-03-22 12:59 ` Paul Waring
2005-03-22 13:22 ` Francesco Riosa
2005-03-22 15:03 ` Simon Stelling
2005-03-22 14:39 ` Stroller
2005-03-22 23:58 ` Ricardo Correia
2005-03-22 23:58 ` Ricardo Correia
2005-03-23 11:15 ` Fabian Zeindl
2005-03-23 18:03 ` Marius Mauch
2005-03-22 13:55 ` Patrick Lauer
2005-03-22 15:19 ` Simon Stelling
2005-03-22 23:58 ` Ricardo Correia
2005-03-23 22:15 ` Nick Rout
2005-03-23 22:49 ` Ricardo Correia [this message]
2005-03-24 14:11 ` Karl Trygve Kalleberg
2005-03-25 7:57 ` Brian Harring
2005-03-26 12:45 ` Karl Trygve Kalleberg
2005-03-27 19:03 ` Brian Harring
2005-03-28 13:04 ` Petteri Räty
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=200503232249.47445.gentoo-dev@wizy.org \
--to=gentoo-dev@wizy.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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