> This may be a silly question, but has hardware been checked? I would
> start by checking: network wiring to the machine; the machine's RAM.
I don't mind silly; I'm just that desperate. I'll do what I can to check those
things, but given that I've seen the same results with the test server on a
On Thu, Sep 26, 2024 at 4:57 PM Williams, James P. {Jim} (JSC-CD4)[KBR
Wyle Services, LLC] via users wrote:
>
> I was pulled away from this problem, so I quoted our last exchange. Daniel,
> you asked to test svn co but keeping communications entirely on the server
> machine. I did that by usin
I was pulled away from this problem, so I quoted our last exchange. Daniel,
you asked to test svn co but keeping communications entirely on the server
machine. I did that by using an https://localhost URL. I also had to turn off
Kerberos authentication, use "Require all granted", and hide the
On 2024-09-25 22:30:40 +0900, Yasuhito FUTATSUKI wrote:
> Then nothing is future-proof. We should check changes,
> forever.
So, shouldn't Subversion provide a command (e.g. svn subcommand) to
tell whether some directory is a working copy? The command should
either give the answer, with a zero exit
