[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: |
Thu, 15 Feb 2018 21:24:54 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Hello Steven,
* On Thu, Feb 15, 2018 at 08:15:06PM +0000 Glasgow, Steven R CIV USARMY TRAC
(US) wrote:
> The file is no longer there. This error occurred on Feb 01 according
> to a log file we maintain. We just noticed that the entire module did
> not get tagged. Could it be that a subsequent process to that area of
> the module already removed the lock sometime between then and now?
>
> I wish the file was still there, but it's not.
>
> Why would a lock file not get deleted?
Ok, then I misunderstood you. I thought you had a permanent problem.
In this case, I assume two people tried to work on the same file at the
same time. That's how CVS handles this issue, by giving this error
message.
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,
Spiro Trikaliotis <=
- Re: CVS lock issue, Thorsten Glaser, 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, 2018/02/16
- 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