Dear Matthias Kranz,
As a general note - I think you should read the things and try to understand
what they mean....
Example:
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > WinCvs support
> > Subscribe to the cvs mailing list.
>
> ? Please admit, that one could get the opinion that the cvs mailing list
> is the list for WinCVS support. At least I did, as I read the page.
Please admit that it doesn't say "wincvs mailing list'. Period.
WinCvs page is clear about that, I didn't have the problem to see the
difference between cvs and wincvs....
> > 3. Comments and suggestion DOES not point to the cvs mailing list.
>
> Hm, I am on the web for several years now and in most cases, those
> bottom addresses are associated with the web master ... ;).
? Do you not read the things just guess what is written there 'in most
cases'? Feel sorry for yourself then...
> ? Please provide where the problem in commandline CVS is? If I remember
> correctly, I took the same steps as the original poster (who did it with
> WinCVS) and got no problems.
>From: <[EMAIL PROTECTED]>
>Sent: Tuesday, July 11, 2000 9:36 PM
>Subject: Patches or work-arounds requested for lock problems
<snip>
> 1. lock/unlock does not work for branches
Did you have a locking working on branches? No problem?
>2. locking a first revision i.e. 1.1.1.1 will show (when a log
> of the file is requested) that only 1.1.1.1 is locked.
But in the end the whole file with all branches are locked, which sucks
because the log only tells about one revision and it makes it difficult to
confirm if the file is locked or not. Status also don't give that info - and
it should.
Still no problem?
OK, here is the conversation wit the problem.
I lock the 1.1.1.1, then I can not commit nor unlock.
cvs -z4 admin -l CvsIn.def (in directory D:\Jerzy\CvsIn)
RCS file: D:\CVS_LocalRepo/CvsIn/CvsIn.def,v
1.1.1.1 locked
done
*****CVS exited normally with code 0*****
cvs -z4 edit CvsIn.def (in directory D:\Jerzy\CvsIn)
*****CVS exited normally with code 0*****
Saved settings for D:\Jerzy successfully...
cvs -z4 commit -m test CvsIn.def (in directory D:\Jerzy\CvsIn)
Checking in CvsIn.def;
D:\CVS_LocalRepo/CvsIn/CvsIn.def,v <-- CvsIn.def
cvs commit: D:\CVS_LocalRepo/CvsIn/CvsIn.def,v: multiple revisions locked by
jerzy.kaczorowski; please specify one
cvs commit: could not check in CvsIn.def
cvs commit: D:\CVS_LocalRepo/CvsIn/CvsIn.def,v: multiple revisions locked by
jerzy.kaczorowski; please specify one
cvs commit: could not unlock D:\CVS_LocalRepo/CvsIn/CvsIn.def,v
*****CVS exited normally with code 1*****
cvs -z4 admin -u CvsIn.def (in directory D:\Jerzy\CvsIn)
RCS file: D:\CVS_LocalRepo/CvsIn/CvsIn.def,v
cvs admin: D:\CVS_LocalRepo/CvsIn/CvsIn.def,v: multiple revisions locked by
jerzy.kaczorowski; please specify one
cvs admin: cannot modify RCS file for `CvsIn.def'
*****CVS exited normally with code 1*****
Still no problem?
And not, it is not WinCvs, it is CVS failing here.
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
