| From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) |> From: davidsen@ariel.crd.GE.COM (william E Davidsen) |> At the risk of sounding as if I'm complaining (rest deleted...) | Don't take the newest version then! (flame flame flame...) My my. Aren't we getting rather jumpy lately? I'm not trying to single these two out, but there has been a lot of "complaining" and flaming responses in return. comp.os.linux is turning into a regular shooting gallery. Do we all drink too much coffee? May I please suggest to those who are awful quick to post flames and counter-rebuttals that we are over- reacting. theory #1> Most of the folks who allegedly "bitch" are new to either unix, usenet, Linux, or social skills. These naive, innocent people do not deserve the pouncing on they sometimes receive. theory #2> Some alleged "bitching" are from people who are making casual observations or bringing out to light some ideas that might make things easier or more understandable. These people do not deserve soap box speeches on how they should do it themselves or take a hike. theory #3> Those posts which are true-blue complaints that have no excuse, should either be ignored, or flamed in private (e-mail). The poor sap could easily ignore the flaming responses in the newsgroup, but if you fill up his mailbox or however he gets his email, it's not so easy; therefore, it is more effective. Don't clutter the bandwidth with it. It is a shame that the psychology behind the net allows otherwise mild-mannered people to turn into raging fiends and bash and burn those who "irritate" them, all because they are hidden behind the fascade of the network. So, please, gentlepeople, I beg of you: think twice about flaming that poor soul who made you believe that you are so superior. We are all human. Just ignore him. He'll go away. Or send (email, not post) him/her a polite message in an honest effort to straighten him out. If you need to blow off some steam, then write an inflamatory note using four-letter words that would make a sailor blush, and then mail it to dev/null. Oh, and don't flame me because I fall into both theories 1 and 2. john
| David Miller | [GIT]: Networking |
| Fred . | Please add ZFS support (from GPL sources) |
| Linus Torvalds | Linux 2.6.26-rc4 |
| Jan Engelhardt | Re: why does x86 "make defconfig" build a single, lonely module? |
git: | |
| Jörg Sommer | [PATCH 2/4] Rework redo_merge |
| Matthieu Moy | git push to a non-bare repository |
| Michael Dressel | git merge --no-commit <branch>; does commit |
| Joakim Tjernlund | [FEATURE REQUEST] git clone, just clone selected branches? |
| Daniel Ouellet | identifying sparse files and get ride of them trick available? |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Unix Fan | Re: Vulnerability Note VU#800113 - Multiple DNS implementations vulnerable to cach... |
| Ihar Hrachyshka | Re: That whole "Linux stealing our code" thing |
| Daniel Brewer | Re: fsync performance hit on 1.6.1 |
| YAMAMOTO Takashi | yamt-km branch |
| der Mouse | Re: mjf-devfs2 branch |
| Ian Zagorskih | POSIX timer_settime() dosn't set timer in some cases (lost accuracy) |
