kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: el.es.cr@gmail.com (el_es)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: Fix spacing between function name and parentheses
Date: Mon, 20 Oct 2014 09:17:50 +0000 (UTC)	[thread overview]
Message-ID: <loom.20141020T103416-233@post.gmane.org> (raw)
In-Reply-To: 28D75159261EA145A62C015E176CFEF583736A4E@D8SMAIL.denver.cqg

Adrian Cornish <adrianc <at> cqg.com> writes:


> I raise the simple motion that when Nicholas Krause posts - 
> NOBODY responds to him - EVER - under threat of
> torture or whatever - for whatever reason - 
> my joy of lurking here has been ruined by a single IDIOT - 
> if this was nntp he would have wandered off a long time 
> ago with ignores - but I blame this list for constantly
> responding to the TROLL and FEEDING it. DONT DO IT

Unfortunately this isn't the time of NNTP, and since lkml 
(and newbies) always was a mailing list, the only hope is
in respective peoples' killfiles...

We need to assume that the list is being watched 
not only by technically able people, but also by ones who
have just a filter for [PATCH] and don't always get
the difference between Reviewed-by and Acked-by...
AND some that could assume that no-answer to a [PATCH]
equals silent acceptance ... Or if he's con enough,
he could say, oh see all the patches I submitted,
no one ever said anything against them...

(and as Greg K-H once said, a few /accepted/ patches can make
 someone employed...) 

Maybe better to introduce a standard clear marker that
able people just respond with, to alikes of nick:

REJECTED-by: Name <address@email.server>

single line, maybe add 1 line of technical explanation 
and DO NOT react* to any further emails demanding further explanation.

(* e.g. place on kill file in your private MUA, so the only way
 they can ever get un-ignored is IFF they submit VALID patches
 to public list AND they get at least Acked.).

(Rationale:

REJECTED, because Nacked-by contains the 'acked' word...
too easy to overlook.
CAPITALS because they do stand out.

REJECTED also is clear in intent in any english<->native dictionary,

REJECTED is (IMO) also a strong enough word to not need any 
further emotional emits...

It's NOT intended in the way the April Fools like/dislike patches
on Facebook was suggested. Nothing to emotionally react to,
just a signal that THIS PATCH IS NOT GOING TO BE APPLIED.

Also it's a serious word, contrary to Trash-detected-by
or This-is-BS-by or Stay-away-from-my-list-by... 

Only to be used as 'last resort' if someone repeatedly fails
sanity test.

Because alternative is, that the mailing list(s) become invite-only,
and that is not going to happen.
)

el_es

  parent reply	other threads:[~2014-10-20  9:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11  1:55 [PATCH] staging: Fix spacing between function name and parentheses Nicholas Krause
2014-10-11  4:58 ` Sudip Mukherjee
2014-10-11  5:23   ` Dave Tian
2014-10-11  6:08     ` Sudip Mukherjee
2014-10-11  6:11       ` Dave Tian
2014-10-11  8:27         ` Peter Senna Tschudin
2014-10-11  9:45           ` Sudip Mukherjee
2014-10-11  9:53             ` Kristofer Hallin
2014-10-11 13:44               ` nick
2014-10-11 13:46                 ` Kristofer Hallin
2014-10-11 13:52                 ` Hugo Mills
2014-10-11 14:17                   ` nick
2014-10-11 15:25                     ` karthik nayak
2014-10-11 22:18                       ` nick
2014-10-12 22:34                   ` Valdis.Kletnieks at vt.edu
2014-10-13  2:31                     ` nick
2014-10-13  3:15                       ` Valdis.Kletnieks at vt.edu
2014-10-13  4:55                     ` Sudip Mukherjee
2014-10-14 15:38                       ` Adrian Cornish
2014-10-14 18:11                         ` Kernel Apprentice
2014-10-14 21:08                         ` John de la Garza
2014-10-20  9:17                         ` el_es [this message]
2014-11-02  0:34                           ` Valdis.Kletnieks at vt.edu
2014-11-03 10:05                             ` Bjørn Mork
2014-11-04  2:23                               ` nick
2014-10-11 14:24                 ` Robert P. J. Day

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=loom.20141020T103416-233@post.gmane.org \
    --to=el.es.cr@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).