From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: Fix spacing between function name and parentheses
Date: Sat, 01 Nov 2014 20:34:45 -0400 [thread overview]
Message-ID: <73141.1414888485@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 20 Oct 2014 09:17:50 -0000." <loom.20141020T103416-233@post.gmane.org>
On Mon, 20 Oct 2014 09:17:50 -0000, el_es said:
> Maybe better to introduce a standard clear marker that
> able people just respond with, to alikes of nick:
>
> REJECTED-by: Name <address@email.server>
We already do something like this.
You'll on occasion see 'Nacked-By: ...' go by when a kernel hacker
wants to denote their displeasure with a given patch. It's up to the
maintainer to decide how much credence to give to the Nack, based on the
relative reputations of the person submitting the patch and the person
nacking it, and any technical grounds given with the nack.
So for instance, if Al Viro sticks a Nacked-By: on a submission, it's
going to be *really* hard to get a maintainer to accept the patch, because
Al has a very long history of almost always being right about such things.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141101/53c6e3d0/attachment.bin
next prev parent reply other threads:[~2014-11-02 0:34 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
2014-11-02 0:34 ` Valdis.Kletnieks at vt.edu [this message]
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=73141.1414888485@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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).