All of lore.kernel.org
 help / color / mirror / Atom feed
From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: New member
Date: Tue, 27 Jan 2015 10:13:55 +0100	[thread overview]
Message-ID: <87fvawwppo.fsf@nemi.mork.no> (raw)
In-Reply-To: <20150126221354.GA16737@crux.local> (John de la Garza's message of "Mon, 26 Jan 2015 14:13:55 -0800")

John de la Garza <john@jjdev.com> writes:
> On Sun, Jan 25, 2015 at 08:10:15PM +0000, Anuz Pratap Singh Tomar wrote:
>> On Sun, Jan 25, 2015 at 7:38 PM, srinivas bakki <srinivas.bakki@gmail.com>
>> wrote:
>> 
>> > Valdis,
>> >            You got to be polite with people.Not everybody is as smart as
>> > you, but they would like to contribute. Just keep in in mind that there's
>> > no future for linux without such people. You cannot keep bullying everybody
>> > like this.
>> >
>> 
>> Talking about polite, you are Top posting, how rude is that?
>
> I thought the post was very helpfull and not rude at all.  I guess we
> all perceive things differently.

This document is written for the Debian project, but I believe it's a
good guide to any open mailing list:
https://www.debian.org/code_of_conduct

I am pretty sure all participants in this thread are trying to help. But
I will ask you all to consider the "In case of problems" section of that
document before continuing this discussion.  In particular:

 "Assume good faith; it is more likely that participants are unaware of
  their bad behaviour than that they intentionally try to degrade the
  quality of the discussion."


In my experience, you will miss a lot if you disregard articles you find
"rude".  Direct and concise advice might sometimes come out harsher than
it was meant.  It doesn't make the advice any less worth. On the
contrary.


Thanks,
Bj?rn

  reply	other threads:[~2015-01-27  9:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 18:07 New member Satwantjit Kaur
2015-01-25 18:31 ` Valdis.Kletnieks at vt.edu
2015-01-25 19:16   ` Surendra Patil
     [not found]     ` <CAHzVKCBVrPfWG4oOW4M0zpc3r48SgraxgdfzNCZtZUJPeW1UZQ@mail.gmail.com>
2015-01-25 19:38       ` Fwd: " srinivas bakki
2015-01-25 20:10         ` Anuz Pratap Singh Tomar
2015-01-25 20:16           ` srinivas bakki
2015-01-25 20:31             ` Anuz Pratap Singh Tomar
2015-01-25 20:38               ` srinivas bakki
2015-01-25 20:42                 ` Anuz Pratap Singh Tomar
2015-01-25 21:29               ` Robert P. J. Day
2015-01-25 21:43                 ` Jonathan Jin
2015-01-25 21:47                   ` Robert P. J. Day
2015-01-26  0:18                     ` Jeshwanth Kumar N K
2015-01-26  0:29                       ` Robert P. J. Day
2015-01-26  1:28                         ` Jeshwanth Kumar N K
2015-01-26  3:45                         ` Valdis.Kletnieks at vt.edu
2015-01-26  6:56                           ` Anand Moon
2015-01-26 10:11                           ` Silvan Jegen
2015-01-26 22:20             ` John de la Garza
2015-01-26 22:13           ` John de la Garza
2015-01-27  9:13             ` Bjørn Mork [this message]
2015-01-25 19:48   ` Robert P. J. Day
2015-01-25 20:01     ` srinivas bakki
2015-01-26 11:53 ` Mulyadi Santosa
2015-01-27 17:32 ` Albert Coder
2015-01-27 17:52   ` Satwantjit Kaur

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=87fvawwppo.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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.