[Top][All Lists]

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

Re: [Gnu-arch-users] the state of the union

From: Andrew Suffield
Subject: Re: [Gnu-arch-users] the state of the union
Date: Thu, 19 Aug 2004 17:43:14 +0100
User-agent: Mutt/1.5.6+20040803i

On Thu, Aug 19, 2004 at 03:42:54AM -0400, Greg Hudson wrote:
> > Client-side caches and memos are a flexible solution that scales
> > arbitrarily with the number of clients.
> Perhaps.
> Here's something I do often: I find a bug in one of the dozens of
> upstream programs I maintain builds of, and I narrow it down to a
> particular source file.  My first question is "is there an upstream
> fix?"  So I ask the upstream CVS repository for a log (or in some cases
> a blame annotation) of the upstream file.  I'm not going to have a
> well-populated client-side cache for the given program.  The upstream
> repository would probably rather not serve me the project's entire
> version history, and I certainly would rather not have my client pore
> through that entire history.

You're muddling up various definitions of "client". The cache is in
the arch client on the server running the archive browser.

If there weren't enough people to make it worth running such a browser
for a given project (which should be a cheap thing to do) - yeah, it
really isn't common enough to matter for that project.

  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' : |
 `. `'                          |
   `-             -><-          |

Attachment: signature.asc
Description: Digital signature

reply via email to

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