[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: |
Tom Lord |
Subject: |
Re: [Gnu-arch-users] the state of the union |
Date: |
Thu, 19 Aug 2004 14:44:57 -0700 (PDT) |
> From: Andrew Suffield <address@hidden>
> > 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.
Which is one of the major points of the whole tiny-core-archive with
ancillary-caches-and-memos things: it lets you get minimal
functionality almost for free but also lets you build out in response
to demand, essentially indefinately.
-t
- [Gnu-arch-users] Re: the state of the union, (continued)
Re: [Gnu-arch-users] the state of the union, Greg Hudson, 2004/08/18
Message not available
Re: [Gnu-arch-users] the state of the union, Tom Lord, 2004/08/18
Re: [Gnu-arch-users] the state of the union, James Blackwell, 2004/08/25