Adam Tkac <atkac <at> redhat.com> writes: > Let me try explain situation around vnc. I'm vnc maintainer and our > current Xvnc has HUGE patches. It is absolutely unmaintained by > upstream so I think it's better fork it because we need vnc server deleted > together. So in the end it looks that I will stop baracuda project, > use patches from it to current vnc and join to TightVNC project. When > TightVNC will be usable we will use it as our default vnc. Btw if you It sounds like you are doing a great job on this - and that the intentions seem perfectly reasonable. I am sure many will appreciate it when the new version is ready for action. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
