We contracted this this morning, though some people got it yesterday. We have generated a quick fix today, that has worked for us. it can be got from: http://www.gotan.org/tmp/scripts.zip enjoy, Tim.
No matter what else you do, get a source code control plan together. use a CVS archive or whatever. This is essential, as alot of projects will just grow if you let them, and trying to pu stuff into a meaningfull source code control system after the fact is a pain in the bol^H^H^Hneck.
Look,/. is a community, that like any 'movement' has a power. This issue is a problem, and possibly the first of many. So why not use the./ effect to influence it. The idea being that an email address is posted for someone qualified/responsble to address this issue with. I beleive that once the feeling is known that this is a sh*ty thing to do, the big PR blunder they have made (./ being a linix users reference) then its self evident. Enough people saying oy and a message to the effect that we will not stand for this kind of thing, then they have to change their ways (or similar). Because we are after all their target market with this product Even so, their PR people will still have a nightmare on their hands once this spreads to the mainstream media. You can just imagine it. So, the idea is, the muscle is there, why not flex it. But, the other issue is there. the community contains alot of '1eet haxxors' that feel that an email composed to be sent diretly to/dev/null, is a valid form of communication. If you are thinking of sending such an email then i will explain in terms you can understand. Fek off and learn some rational discorse before the lack of it does you a personal injury. :) Tim.
Slashdot Mirror
Here, i have a bridge to sell you! not interested in a bridge? sorry i meant a wall.......
Fsck these guys.
We contracted this this morning, though some people got it yesterday. We have generated a quick fix today, that has worked for us. it can be got from: http://www.gotan.org/tmp/scripts.zip enjoy, Tim.
No matter what else you do, get a source code control plan together. use a CVS archive or whatever. This is essential, as alot of projects will just grow if you let them, and trying to pu stuff into a meaningfull source code control system after the fact is a pain in the bol^H^H^Hneck.
Look, /. is a community, that like any 'movement' has a power. ./ effect to influence it. /dev/null, is a valid form of communication. If you are thinking of sending such an email then i will explain in terms you can understand. Fek off and learn some rational discorse before the lack of it does you a personal injury.
:)
This issue is a problem, and possibly the first of many. So why not use the
The idea being that an email address is posted for someone qualified/responsble to address this issue with.
I beleive that once the feeling is known that this is a sh*ty thing to do, the big PR blunder they have made (./ being a linix users reference) then its self evident. Enough people saying oy and a message to the effect that we will not stand for this kind of thing, then they have to change their ways (or similar). Because we are after all their target market with this product Even so, their PR people will still have a nightmare on their hands once this spreads to the mainstream media. You can just imagine it.
So, the idea is, the muscle is there, why not flex it.
But, the other issue is there. the community contains alot of '1eet haxxors' that feel that an email composed to be sent diretly to
Tim.