kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: Fix spacing between function name and parentheses
Date: Mon, 03 Nov 2014 21:23:03 -0500	[thread overview]
Message-ID: <54583887.8030504@gmail.com> (raw)
In-Reply-To: <8761ewzji4.fsf@nemi.mork.no>

Greetings Bjorn and others,
I sent this patch a few weeks ago and am really trying to to improve my rep here by sending solid patches.
In addition I understand the caution with my patches due to my terrible rep but it would be nice if someone
sends or acknowledges the patch as other people on this list have stated it's correct and good in previous 
emails to me. 
Nick

On 14-11-03 05:05 AM, Bj?rn Mork wrote:
> Valdis.Kletnieks at vt.edu writes:
>> 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.
> 
> Yes, but the technical grounds are still the reason the patch is not
> accepted.  Which is why a formalized nak is pointless.  It has no value
> without a verbose explanation of the technical grounds behind it. If Al
> Viro, or anyone else, use a simple one-line reject message, then I am
> pretty sure that is because they have already explained their objections
> somewhere else. I don't think anyone can reject anything merely on their
> personal reputation. And there is nowhere to record naks, so a standard
> label just isn't needed.
> 
> Rejecting is completely different from e.g. Acked-by, which both is a
> complete explanation ("I am fine with this patch as it is") and is
> recorded for future reference in the commit message.
> 
> 
> Bj?rn
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

  reply	other threads:[~2014-11-04  2:23 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
2014-11-03 10:05                             ` Bjørn Mork
2014-11-04  2:23                               ` nick [this message]
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=54583887.8030504@gmail.com \
    --to=xerofoify@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).