Dan Peterson writes:
>
> Has the "-n" option always ignored the lock?
I think so. It's certainly been true for quite a while.
> I've run into this type of problem in the past, ie, if a loginfo script
> tries to run "cvs rlog" it get's "waiting for lock" messages because the
> original commit st
In response to a question about getting additional information from within
an *info script:
On Sat, 21 Jun 2003 Larry Jones wrote:
> You can run "cvs -n status" (the -n causes it to ignore the lock that's
> in place for the in-progress commit).
Has the "-n" option always ignored the lock?
I've
