[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: situations where cached revisions are not so go

From: Jason McCarty
Subject: Re: [Gnu-arch-users] Re: situations where cached revisions are not so good
Date: Wed, 24 Sep 2003 23:02:49 -0400
User-agent: Mutt/1.5.4i

Miles Bader wrote:
> I typically update from Tom's sources after reading an email message
> saying `just added feature X,' so the long latency of a cron-updated
> mirror is a burden (usually what would happen is, I'd do an update, see
> nothing changed, be puzzled for a split-second, and then go "oh yeah"
> and update my local mirror and try again).  It also turned out that the
> actual amount of data transfer was _more_ with the mirror than with a
> direct connection, because I typically only do a few operations; with a
> mirror, I either had to remember to use a very specific limit for the
> mirroring command (and worry about what it should be -- it depends on
> what changed), but the direct connection basically transfers exactly
> what I need.

Having to give a certain limit argument to keep a minimal mirror is why
I proposed a --revisions-only argument to push-mirror last week. It
seems like a very useful option (it would push only revisions whose
version already existed in your local mirror). Too bad I don't have
enough time to implement it ;-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]