On 16 May 2006, at 04:08, Scott B. wrote:
Just because YOU aren’t interested an automated script, that
doesn’t mean that nobody is.
Never said that did I? Put your capitals back in their box.
On 16 May 2006, at 08:55, Kester Dobson wrote:
The proxy issue was my main purpose for doing this, couldn’t get
access to it from work - and suspect many people are in the same
situation. Additionally downloading, reading up on and operating a SVN
client seems a little much overhead for trying out the current trunk.
I thought your main purpose was because your host didn’t support
Some svn clients are exactly like FTP clients. Are you mistaking
them with the command line client - which is tricky for beginners
to grasp? Do you understand that I didn’t see the point because even
though a host doesn’t support svn … you can still use svn on your
own machine? It’s much easier to use because instead of having to
grab the whole source every time you only grab the changed files.
You can easily get six changesets at a weekend.
Maybe I should have made it clearer that I didn’t see the need for an
automated script if you’re host doesn’t support svn, because you
don’t need your host to support svn.
I don’t quite get the proxy thing. I wouldn’t have thought
typosphere was a regularly blocked site and if people are at work
then they’re work … not playing with typo code.
Er and just for the record that doesn’t mean I hate proxies
My motives are to provide the tarballed sources, but I can understand
how the ads made it look - I have now removed them.
To be honest if you’re providing a service that could suck down
bandwidth I wouldn’t blame you for putting ads up there. That’s not
a click farm … that’s an ad supported service.