Displaying 4 results from an estimated 4 matches for "vounteer".
Did you mean:
volunteer
2005 Aug 03
3
debs for 1.0?
...http://src.braincells.com/dovecot-test/).
Even though google turns up
http://hemma.tobbe.nu/debian/mini-dinstall/incoming/dovecot_1.0.test46-1_i386.changes
searching for dovecot on packages.debian.org (any distribution
or source) only yields 0.99.14 and 0.99.20050712.
I know Jaldhar called for vounteers to take over, but I don't
feel qualified... but I've managed to do away with all non-deb
installations, so if I have to I'll make a .deb myself, is there
maybe an already-written script to do that with dovecot?
Thanks for suggestions.
2008 Jul 30
0
[LLVMdev] Is there room for another build system?
...within CMake itself (with some
effort, of course). I lack the knowledge to judge the points you raise
about distribution, package creation, etc. Finally, IMHO your concers
about CMake not preserving as many [autotools] feautures as [it] can,
does not apply to LLVM, at least as there is someone who vounteers to do
the replication work :-)
Please, some LLVM release manager (Tanya?), read Albert's web page and
evaluate how much impact have the issues he raises on your work.
--
Oscar
2025 Mar 07
4
Support for transferring sparse files via scp/sftp correctly?
...that sparse files are not handled correctly
> and fix it
You and the others on this thread are IIRC the first people in sftp's
24 year history to ever ask for sparse file support. Its absence is not
a bug and adding it will almost certainly require new protocol extensions.
Being pushy with vounteer developers, telling us what our priorities
should be, assigning us work, etc. will not have the result you want.
If you want this to happen, I recommend starting by figuring out what
protocol extensions need to be made, and how to support sparse files
on system without SEEK_DATA/HOLE - it should b...
2008 Jul 30
3
[LLVMdev] Is there room for another build system?
Duncan Sands wrote:
> Do ordinary users need to have cmake if they want to build llvm?
> If so, that's bad because they'll have to install it (unlike the
> current setup, where only very standard tools are needed).
That's not the only problem with cmake. The autotools may be a big and
ugly beast, but that's because they're trying to solve a big and ugly
problem for