[cvsnt] Is this a CVS bug ?

[Loïc Bertholet]

By locked revision I mean puting lock by command : cvs admin -l myResource.
It's possible to put lock on branch revision by using cvs admin -lMyBranch
myResource.

In fact we are not talking about same "locks"....

----- Original Message -----
From: "Tony Hoyle" <tmh at nodomain.org>
Newsgroups: support.cvsnt
To: <cvsnt at cvsnt.org>
Sent: Wednesday, August 13, 2003 6:46 PM
Subject: Re: [cvsnt] Is this a CVS bug ?


> On Wed, 13 Aug 2003 17:05:31 +0200, Loïc Bertholet <lbertholet at sysdeo.com>
> wrote:
>
> >According to my test, if a file (any revision)  is commited and has only
one
> >revision locked, it is no longer locked.
> >If a file has 2 revisions locked and one of these revisions is commited,
> >file is no longer locked (both revisions are unlocked). But if a unlocked
> >revision is committed, file is still locked (both revision skeep locked).
> >Moreover if a file has 3 revisions locked and one of these revision is
> >commited, file is still locked (the 2 other revisions keep locked)
> >
> >Is this a bug or normal behaviour ?
> >
> I'm not sure what you mean by a locked revision.  Files are locked, not
> revisions (which wouldn't make a lot of sense).
>
> Doing edit -c on multiple branches doesn't work, because the underlying
edit
> mechanism doesn't store the branch that is being edited...  Changing that
> would probably mean breaking the edit mechanism so it isn't something
that's
> even going to be thought about yet (nobody has complained about it in 3.5
> years though so I expect it's not causing any grief).
>
> Tony
>
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
>
>