[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Non-DoD Source] Re: CVS lock issue
From: |
Spiro Trikaliotis |
Subject: |
Re: [Non-DoD Source] Re: CVS lock issue |
Date: |
Fri, 16 Feb 2018 10:58:31 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Hello Thorsten,
* On Thu, Feb 15, 2018 at 08:40:03PM +0000 Thorsten Glaser wrote:
> Spiro Trikaliotis dixit:
>
> >No, unfortunately, that's not how CVS works. There is no wait for the
> >lock.
>
> This is wrong, I’ve seen waits for locks, at least between two
> concurrent commit operations.
You're right, I was wrong. CVS waits for locks, but it this is not
always successfull, so it fails in some cases. Because it fails
sometimes, I said that it fails always, which is clearly wrong.
Best regards,
Spiro.
--
Spiro R. Trikaliotis
http://www.trikaliotis.net/
- CVS lock issue, Glasgow, Steven R CIV USARMY TRAC (US), 2018/02/15
- Re: CVS lock issue, Spiro Trikaliotis, 2018/02/15
- RE: [Non-DoD Source] Re: CVS lock issue, Glasgow, Steven R CIV USARMY TRAC (US), 2018/02/15
- RE: [Non-DoD Source] Re: CVS lock issue, Glasgow, Steven R CIV USARMY TRAC (US), 2018/02/15
- Re: [Non-DoD Source] Re: CVS lock issue, Spiro Trikaliotis, 2018/02/15
- Re: [Non-DoD Source] Re: CVS lock issue, Thorsten Glaser, 2018/02/15
- Re: [Non-DoD Source] Re: CVS lock issue,
Spiro Trikaliotis <=
- RE: [Non-DoD Source] Re: CVS lock issue, Glasgow, Steven R CIV USARMY TRAC (US), 2018/02/16
- Re: [Non-DoD Source] Re: CVS lock issue, Mark D. Baushke, 2018/02/16
Re: CVS lock issue, Thorsten Glaser, 2018/02/15