public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: emerge-webrsync bandwidth improvement
Date: Wed, 4 May 2005 22:02:35 -0500	[thread overview]
Message-ID: <20050505030235.GA13705@exodus.wit.org> (raw)
In-Reply-To: <4278BF96.2000909@b-i-t.de>

On Wed, May 04, 2005 at 02:27:02PM +0200, sf wrote:
> Is there any way to skip syncing if no patches are found? emerge sync
> uses a timestamp for that purpose, doesn't it?

Could, yes.  Few more pressing things re: emerge-delta-webrsync, 
namely (order of what I'm hacking on now)

A) bzip2 v1.03 is stabled now.  MD5 compressor issue _will_ bite  
   emerge-delta-webrsync in the ass _soon_ .  Should have a version 
   bump that handles this tomorrow or friday at the latest.
B) Permenant solution needed for when snapshots upstream aren't 
   generated, as occured 04/29.  This probably will have to be 
   serverside- easiest route, otherwise have to implement version 
   jumping logic in bash, which is ugly
C) cleansing of old snapshots.  Current 'handling' of it (read: not 
   doing a damn thing) is ugly.  :)

So... re: your request, emerge-webrsync default behaviour actually is 
to sync, regardless if an update was pulled or not.  I'd rather not 
deviate from the default behaviour of emerge-webrsync, but tacking in 
support for a command opt (say -u for 'update only'?) can be slipped 
out at some point.

Thoughts?
~brian
-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-05  3:02 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 ` [gentoo-dev] " sf
2005-05-05  3:02   ` Brian Harring [this message]
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=20050505030235.GA13705@exodus.wit.org \
    --to=ferringb@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