Thomas Sachau: > > I don't understand why specifyin O=3D means to waste resources. > > Currently I am thinking these are the main reason of your problem. > > - you want to put the kernel source dir readonly > > - you don't specify O=3D > > You want to prepare another kernel dir and want to call a kernel script a= > nd all of that just to > remove a word from a text file. And you dont understand, why that is a wa= > ste of resources? While > just opening the file in an editor and removing that word would exactly d= > o the same? And committing > that changed file to git would fix it once and for all.
Not for all. It is only for people who has their own rule like yours. I don't understand why you can assure it is once. If you really think so, why don't you do it in your git tree and git pull your private changes? Still I don't know why O= is a waste of resources, nor why you wrote an example of opening a file. > Oh and for the kernel source dir being readonly: There is a pretty simple= > reason for it: > > It prevents random scripts to play with my live system at will instead of= > keeping itself inside the > builddir as it should. That is exactly what O= is for. J. R. Okajima ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev
