On Wed, Dec 03, 2008 at 10:30:46PM -0500, Taylor Venable wrote: > > On Wed, 3 Dec 2008 13:51:20 +0100 > Marc Weber <[EMAIL PROTECTED]> wrote: > > > On the other hand have you had a look at all those C lines within the > > kernel? Or all the other applications you are using? > > But most projects, let's take OpenBSD for example, don't have a totally > open commit process. I trust the small party of people who do examine > every single line of the kernel on my behalf, so there's no need for me > to look at it myself. And I only use what they publish, so I can be > reasonably certain the code is good. But in a world where anybody could > commit something, I could not trust it at all, because I cannot trust > the whole world. > > You have to take some risk. Who knows wether vim.org can be hacked as > > well? You're right, it has been shown that was doable to became a debian, gonteoo, mandrake update server thereby preventing clients to get security updates. Moreover the "update" server already had the ips of its clients.. Anyway I think this is fixed because I've moved to github. Only I have access to it. So you have to trust me :-) Anyone else can send me pull requests though. You still can push to mawercer without access restrictions. But I'll review the patches before uploading them to github.
> certain that what you're downloading is what the author intended. > Features like this (done automatically by many package managers) would > be a nice addition. So would you like to join and give some input while testing? Perhaps some > inspiration could be drawn from the attempts that other editors, e.g. > (X)Emacs have made in this arena as well. What can we learn from them? I've never used them to that extend. Sincerly Marc Weber --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
