public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: sf <sf@b-i-t.de>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-user@lists.gentoo.org
Subject: [gentoo-dev]  Re: emerge-webrsync bandwidth improvement
Date: Wed, 04 May 2005 14:27:02 +0200	[thread overview]
Message-ID: <4278BF96.2000909@b-i-t.de> (raw)
In-Reply-To: <20050422130151.GB16038@exodus.wit.org>

Brian Harring wrote:
...
> It's a work in progress, but it's been functional without any major 
> bugs for a few weeks now, so if you're interested, take it for a spin.

Thanks in advance for your effort.

On first invocation emerge-delta-webrsync pulled a complete snapshot (as
described in your blog). On second invocation I got:

Looking for available base versions for a delta
fetching patches
failed fetching snapshot-20050503-20050504.patch.bz2.md5sum
no patches found? up to date?  syncing
Syncing local tree...
building file list ...
114391 files to consider

Number of files: 114391
Number of files transferred: 0
Total file size: 89923713 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 2701117
Total bytes written: 2701170
Total bytes read: 20

wrote 2701170 bytes  read 20 bytes  125636.74 bytes/sec
total size is 89923713  speedup is 33.29
cleaning up
transferring metadata/cache
skipping sync

>>> Updating Portage cache:  100%


Is there any way to skip syncing if no patches are found? emerge sync
uses a timestamp for that purpose, doesn't it?

Regards
	Stephan

-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-04 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 13:01 [gentoo-dev] emerge-webrsync bandwidth improvement Brian Harring
2005-05-04 12:27 ` sf [this message]
2005-05-05  3:02   ` [gentoo-dev] " Brian Harring
2005-05-09  7:09     ` sf
2005-05-09 10:50       ` Brian Harring

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=4278BF96.2000909@b-i-t.de \
    --to=sf@b-i-t.de \
    --cc=gentoo-dev@lists.gentoo.org \
    --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