All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	Michael Haggerty <mhagger@alum.mit.edu>,
	Git List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	A Large Angry SCM <gitzilla@gmail.com>
Subject: Re: [PATCH] Documentation/CommunityGuidelines
Date: Tue, 11 Jun 2013 17:41:00 +0200	[thread overview]
Message-ID: <87obbc4pv7.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <CAMP44s2fZemrqrBQGwFduE3dYs6S_dBO1fwpbfyDPn+jovze-Q@mail.gmail.com> (Felipe Contreras's message of "Tue, 11 Jun 2013 10:06:07 -0500")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> On Tue, Jun 11, 2013 at 7:33 AM, Thomas Rast <trast@inf.ethz.ch> wrote:
>
>> My approach -- and in my perception also that preferred by most of the
>> regulars who have spoken in this whole mess -- is that since there is a
>> fire hazard, it would be more effective firefighting to just remove the
>> hazard, thus preventing future fires.
>
> You would make an excellent evil dictator.
>
> A benevolent dictator like Linus Torvalds knows better, in the LKML
> "fire hazards" are not removed, they are ignored before any flames go
> up. This achieves the best of both worlds; if the person is truly
> vicious, nothing happens, but if there's something to it, a person
> that doesn't offend so easily might have a fruitful discussion, while
> the rest ignore the thread.
>
> In a flamewar everyone is guilty. Apparently you never learned that
> "but he started it!" is not a defense worthy of an adult, hell, even
> most children know that.

[Yes, I should let this thread die, but you are offering me too good a
chance to pass up.]

It's funny that you would mention Linus, considering there's at least
one instance on record where he broke almost every rule that Ram
attempted to set out in the thread starter, calling you among other
things a "fucking moron" and telling you to "go away".

  https://lkml.org/lkml/2012/4/12/434

In case our readers wonder why the flame war suddenly died out at a
depth of about 19 replies, fear not, for the story continued:

  https://plus.google.com/108736516888538655285/posts/7QSVy8taWgC


And before you try to shoot that down, please make sure your argument
also applies to the recurring situation of your repeatedly ignoring
SubmittingPatches as far as commit messages go against explicit requests
to stop that.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2013-06-11 15:41 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 13:28 [PATCH] Documentation/CommunityGuidelines Ramkumar Ramachandra
2013-06-10 13:50 ` Célestin Matte
2013-06-10 14:04   ` Matthieu Moy
2013-06-10 16:25     ` Robin H. Johnson
2013-06-10 17:42       ` Junio C Hamano
2013-06-10 19:01         ` Jonathan Nieder
2013-06-10 19:45           ` Ramkumar Ramachandra
2013-06-10 20:41             ` A Large Angry SCM
2013-06-10 20:56               ` Ramkumar Ramachandra
2013-06-10 21:09                 ` A Large Angry SCM
2013-06-11  5:16         ` Felipe Contreras
2013-06-11  8:56         ` Ramkumar Ramachandra
2013-06-11  4:41 ` Michael Haggerty
2013-06-11  6:28   ` Felipe Contreras
2013-06-11 10:45   ` Ramkumar Ramachandra
2013-06-11 11:49     ` Felipe Contreras
2013-06-11 12:33     ` Thomas Rast
2013-06-11 13:40       ` Ramkumar Ramachandra
2013-06-11 14:40         ` Michael Haggerty
2013-06-11 15:34           ` Felipe Contreras
2013-06-11 18:16           ` Ramkumar Ramachandra
2013-06-11 18:43             ` Michael Haggerty
2013-06-11 18:55               ` Ramkumar Ramachandra
2013-06-11 19:06                 ` Junio C Hamano
2013-06-11 19:39                   ` Felipe Contreras
2013-06-11 23:48               ` Felipe Contreras
2013-06-11 19:55           ` Brandon Casey
2013-06-12 11:56         ` Theodore Ts'o
2013-06-12 12:29           ` Ramkumar Ramachandra
2013-06-12 13:58           ` Felipe Contreras
2013-06-11 15:06       ` Felipe Contreras
2013-06-11 15:41         ` Thomas Rast [this message]
2013-06-11 15:52           ` Felipe Contreras
2013-06-11 16:10   ` Thomas Rast
2013-06-11 16:17     ` Felipe Contreras
2013-06-11 17:00   ` Junio C Hamano
2013-06-11 18:24     ` Michael Haggerty
2013-06-11 18:29     ` John Keeping
2013-06-11 18:46       ` Ramkumar Ramachandra
2013-06-11 19:54         ` John Keeping
2013-06-12 11:26           ` Ramkumar Ramachandra
2013-06-12 13:14             ` John Keeping
2013-06-11 18:52       ` Michael Haggerty
2013-06-11 19:19         ` John Keeping
2013-06-11 19:46         ` Philip Oakley
2013-06-12  0:08           ` John Szakmeister
2013-06-12 14:49           ` Jakub Narebski
2013-06-12 20:54             ` Philip Oakley
2013-06-11 19:35       ` Felipe Contreras
2013-06-11 20:33     ` Jeff King
2013-06-11 20:55       ` Junio C Hamano
2013-06-11 23:19         ` Felipe Contreras
2013-06-12 12:27           ` Theodore Ts'o
2013-06-12 14:06             ` Felipe Contreras
2013-06-12 12:03       ` Ramkumar Ramachandra
2013-06-12 20:02   ` Junio C Hamano
2013-06-13  3:45     ` Michael Haggerty
2013-06-13  4:22       ` Junio C Hamano
2013-06-11  5:38 ` Felipe Contreras
2013-06-11 11:11   ` Ramkumar Ramachandra
2013-06-13 10:19 ` Thomas Adam
2013-06-13 13:36   ` Felipe Contreras
2013-06-14  9:48   ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obbc4pv7.fsf@linux-k42r.v.cablecom.net \
    --to=trast@inf.ethz.ch \
    --cc=artagnon@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitzilla@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=mhagger@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.