Version: 2.0 (using KDE 3.1.3) Installed from: Gentoo Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) OS: Linux (i686) release 2.4.19-gentoo-r9 Sometimes, one want to perform many actions on different files but the CVS repository is slow to respond. I have had some case with a 30s respond time. In such cases, issuing one cvs commands block any further processing until it is finished. I suggest to allow cervisia to queue cvs commands requested by the users, and to execute them one by one. That way, the user can perform man commands, even with a slow reposotiry.
Hi Philippe, I still think about this wish but until then you could take a look at cvsq (http://www.volny.cz/v.slavik/lt/cvsq.html). I haven't tested it myself and I don't know if it works with Cervisia, but it seems to offer the functionality you want. Christian
The homepage seems to have moved: http://metawire.org/~vslavik/sw/cvsq/ Has anyone tried it with Cervisia? About the feature wish itself: wouldn't it be possible to fork the process that does the CVS action and therefor just allow to commit the next file(s) for example while the other operation happens in the background?
Since the cvs commands are executed by the cvs DCOP service, they are already running outside the Cervisia process. It should be possible to create a queue for some specific cvs commands (like e.g. commit, add, remove) which is then processed by worker thread. This thread calls the cvs DCOP service and adds the output to the protocol view. To me more problematic is the presentation of the queue status. So far we just showed a progress dialog after a configurable timeout. IMHO this needs some more thought.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Given that the feature was requested 17 years ago and is still not implemented, I am not sure that it makes sense to keep it open. But the feature request still stands.