It wouldn't be slashdot without the google partner links for early karma-whoring anyway.
In other words, RTFM, newbie.
on
OS X Hacks
·
· Score: 0, Insightful
For my money the last chapter is a complete waste of space since it only covers installing MySQL and PostgresSQL, and if you can't figure out how to install them from the documentation then you aren't smart enough to use them.
Maybe someone would buy the book because he can't figure out the docs? What an ass, to cop an attitude on the authors since some of their audience aren't already MySQL experts.
Or maybe he's just a dumbass. So he's being fired but calling it "resigning to spend more time with his family." Only a moron wouldn't see that he has been given the boot.
Since bugzilla blocks slashdot links (jamie you should KNOW this):
Bugzilla Etiquette
There's a number of faux pas you can commit when using Bugzilla. At the very least, these will make Mozilla contributors upset at you; if committed enough times they will cause those contributors to demand the disabling of your Bugzilla account. So, ignore this advice at your peril.
That said, Mozilla developers are generally a friendly bunch, and will be towards you as long as you follow these guidelines. 1. Commenting
This is the most important section.
1. No pointless comments. Unless you have something constructive and helpful to say, do not add a comment to a bug. In bugs where there is a heated debate going on, you should be even more inclined not to add a comment. Unless you have something new to contribute, then the bug owner is aware of all the issues, and will make a judgement as to what to do. If you agree the bug should be fixed, vote for it. Additional "I see this too" or "It works for me" comments are unnecessary unless they are on a different platform or a significantly different build. 2. No obligation. "Open Source" is not the same as "the developers must do my bidding." The only person who has any obligation to fix the bugs you want fixed is you. Never act as if you expect someone to fix a bug by a particular date or release. This is merely obnoxious, and is likely to get the bug ignored. 3. No personal abuse. Bugzilla is a window into the world of Mozilla development. The fact that we permit anyone with an account to add a comment does not mean you may harass, harangue or otherwise hassle contributors. Do not make weak threats like "I won't use Mozilla until this bug is fixed!" If a respected project contributor complains about your Bugzilla attitude, then you may have your account disabled. If you don't like this possibility, become a respected project contributor.
2. Changing Fields
1. No messing with other people's bugs. Unless you are the bug assignee, or have some say over the use of their time, never change the Priority or Target Milestone fields. If in doubt, do not change the fields of bugs you do not own - add a comment instead, suggesting the change. 2. No whining about decisions. If a respected project contributor has marked a bug as INVALID, then it is invalid. Someone filing another duplicate of it does not change this. Unless you have further important evidence, do not post a comment arguing that an INVALID or WONTFIX bug should be reopened.
3. Applicability
1. Some of these rules may not apply to you. If they do not, you will know exactly which ones do not, and why they do not apply. If you are not sure, then they definitely all apply to you.
If you see someone not following these rules, the first step is to point this out by private mail. They may well not be aware of this document. Flaming people publically in bugs just causes resentment. In the case of persistent offending you should report the matter to Gerv.
This entire document can be summed up in one sentence: do unto others as you would have them do unto you.
Other useful documents: The Bug Writing Guidelines.
This is CmdrTaco's review, as opposed to some other fucker's review, which you are referring to.
If you looked closely (which you did not) you would have noticed that CmdrTaco commented on this very subject just two days ago. I quote: "I have a review unit on my desk, and am super impressed. A larger impression piece will be coming out just as soon as I have time to write it."
Slashdot Mirror
unlike your shrivelled tiny cocks, which just provoke tears and horror.
Dumbass.
dumbass.
It got cancelled! Duh.
Fuckers.
Quit trying to destroy Linux. it's your bread and butter.
I don't.
this set of buttocks!
Yes, but make sure you have showers. And do not hesitate to require people to use them.
It wouldn't be slashdot without the google partner links for early karma-whoring anyway.
Maybe someone would buy the book because he can't figure out the docs? What an ass, to cop an attitude on the authors since some of their audience aren't already MySQL experts.
Or maybe he's just a dumbass. So he's being fired but calling it "resigning to spend more time with his family." Only a moron wouldn't see that he has been given the boot.
Since bugzilla blocks slashdot links (jamie you should KNOW this):
Bugzilla Etiquette
There's a number of faux pas you can commit when using Bugzilla. At the very least, these will make Mozilla contributors upset at you; if committed enough times they will cause those contributors to demand the disabling of your Bugzilla account. So, ignore this advice at your peril.
That said, Mozilla developers are generally a friendly bunch, and will be towards you as long as you follow these guidelines.
1. Commenting
This is the most important section.
1. No pointless comments. Unless you have something constructive and helpful to say, do not add a comment to a bug. In bugs where there is a heated debate going on, you should be even more inclined not to add a comment. Unless you have something new to contribute, then the bug owner is aware of all the issues, and will make a judgement as to what to do. If you agree the bug should be fixed, vote for it. Additional "I see this too" or "It works for me" comments are unnecessary unless they are on a different platform or a significantly different build.
2. No obligation. "Open Source" is not the same as "the developers must do my bidding." The only person who has any obligation to fix the bugs you want fixed is you. Never act as if you expect someone to fix a bug by a particular date or release. This is merely obnoxious, and is likely to get the bug ignored.
3. No personal abuse. Bugzilla is a window into the world of Mozilla development. The fact that we permit anyone with an account to add a comment does not mean you may harass, harangue or otherwise hassle contributors. Do not make weak threats like "I won't use Mozilla until this bug is fixed!" If a respected project contributor complains about your Bugzilla attitude, then you may have your account disabled. If you don't like this possibility, become a respected project contributor.
2. Changing Fields
1. No messing with other people's bugs. Unless you are the bug assignee, or have some say over the use of their time, never change the Priority or Target Milestone fields. If in doubt, do not change the fields of bugs you do not own - add a comment instead, suggesting the change.
2. No whining about decisions. If a respected project contributor has marked a bug as INVALID, then it is invalid. Someone filing another duplicate of it does not change this. Unless you have further important evidence, do not post a comment arguing that an INVALID or WONTFIX bug should be reopened.
3. Applicability
1. Some of these rules may not apply to you. If they do not, you will know exactly which ones do not, and why they do not apply. If you are not sure, then they definitely all apply to you.
If you see someone not following these rules, the first step is to point this out by private mail. They may well not be aware of this document. Flaming people publically in bugs just causes resentment. In the case of persistent offending you should report the matter to Gerv.
This entire document can be summed up in one sentence: do unto others as you would have them do unto you.
Other useful documents: The Bug Writing Guidelines.
That is so fucking old. Try something else for your cut-n-paste.
You're the dumbass by posting the trollbait. Lick my poorly wiped arse.
This is not news. Read sllort's journals from about a year ago for the whole story. Then come on over to the dark side.
Bye-bye Korean Broadband, it was nice to know ya!
Don't you have work to do? Like moving into the Senate basement?
Shit, I didn't know!
Yes, it's the science of sitting on your ass all day and watching teevee. Yeah boy.
A post this foolish could only be from a Dumbass!
This is CmdrTaco's review, as opposed to some other fucker's review, which you are referring to.
If you looked closely (which you did not) you would have noticed that CmdrTaco commented on this very subject just two days ago. I quote: "I have a review unit on my desk, and am super impressed. A larger impression piece will be coming out just as soon as I have time to write it."
Wow, you really are a dumbass!
At least be my freak, okay?
Thank you. Ya smoke? It's your own damn fault, dumbass.
You are most definitely NOT a dumbass to get married. Enjoy!