Hi Joe,
How is it going ?
Have you moved the needle forward ?
Seeing you're running on a VPS, my guess would be an I/O saturation or
big latency, causing subversion taking a very long time to acknowledge
the file has securely been written down on the "hard drive". I've
experienced this quite a
On Tue, Dec 08, 2020 at 03:44:21PM +0300, Anton Shepelev wrote:
> Nathan Hartman:
>
> > A possible rationale is that the HEAD revision could
> > change without your knowledge (e.g., another user commits
> > something in the meantime) and you wouldn't get the
> > revision you were expecting.
> >
>
On Tue, Dec 8, 2020 at 7:44 AM Anton Shepelev wrote:
> Nathan Hartman:
>
> > A possible rationale is that the HEAD revision could
> > change without your knowledge (e.g., another user commits
> > something in the meantime) and you wouldn't get the
> > revision you were expecting.
> >
> > When I
Nathan Hartman:
> A possible rationale is that the HEAD revision could
> change without your knowledge (e.g., another user commits
> something in the meantime) and you wouldn't get the
> revision you were expecting.
>
> When I want to see the diff of the most recent revision I
> use 'svn log -l 1
