Re: cvs tag and #cvs.lock

"Paul Edwards" <[email protected]>
Newsgroups gmane.comp.version-control.cvs.bugs
Organization BigPond Internet Services (http://www.bigpond.net.au)
Message-ID <[email protected]>
"Larry Jones" <[email protected]> wrote in message news:[email protected]...
> Paul Edwards writes:
> >
> > On CVS 1.11.5 on Solaris someone did a "cvs tag" (not rtag)
> > and then ctrl-c'd it, and it left a #cvs.lock in the repository.
> >
> > This is a local repository.
> >
> > Does CVS not handle this cleanly?
>
> It's supposed to -- it works for me.  All I can think of is that someone
> did something more drastic than ctrl-c (like ctrl-\) or managed to do
> ctrl-c a second time before CVS had finished cleaning up.

Multiple ctrl-c's are something that is often seen done by
Unix types (although I don't know about this specific instance).
Should a sig-ignore be done whenever the ctrl-c handler is
invoked to handle "common user practice"?  Or a handler
that says "stop interrupting me, I'm working as fast as I can
on the original instruction"?

BFN.  Paul.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.