From: Krzysztof Halasa <khc@pm.waw.pl>
To: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Scott Preece <sepreece@gmail.com>,
Valdis.Kletnieks@vt.edu, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] document Acked-by:
Date: Sat, 02 Jun 2007 02:56:30 +0200 [thread overview]
Message-ID: <m3lkf341j5.fsf@maximus.localdomain> (raw)
In-Reply-To: <alpine.DEB.0.99.0706012032260.31394@sigma.j-a-k-j.com> (John Anthony Kazos, Jr.'s message of "Fri, 1 Jun 2007 20:37:27 -0400 (EDT)")
"John Anthony Kazos Jr." <jakj@j-a-k-j.com> writes:
> "Acked-by:" does not mean "I like this" but rather "I approve of this".
I'd say it means "I acknowledge it". If you want to express
approval, why not use some sort of "Approved-by"?
> If I put "Acked-by: John..." on a patch of any kind, even trivial, it
> would look incredibly stupid, because I'm just some guy messing around
> with the kernel. A tactful response to me doing that from any actual
> kernel bigwig would be, "I appreciate your enthusiasm, but you are not
> part of the kernel patch flow." Similarly, a tactful response to me
> NACKing a patch would be, "I appreciate your concern, but you are in no
> position to remove a patch from the stream. Your comments will be
> considered and implemented or countered by an actual maintainer."
>
> This is appropriate.
You seem to know these things very well.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-06-02 0:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 2:09 akpm
2007-06-01 5:32 ` Valdis.Kletnieks
2007-06-01 6:10 ` H. Peter Anvin
2007-06-01 10:53 ` John Anthony Kazos Jr.
2007-06-01 19:27 ` Krzysztof Halasa
2007-06-01 19:37 ` Scott Preece
2007-06-01 20:00 ` Andrew Morton
2007-06-01 20:04 ` Andrew Morton
2007-06-02 13:34 ` debian developer
2007-06-02 17:13 ` Jan Engelhardt
2007-06-02 19:34 ` Valdis.Kletnieks
2007-06-01 22:10 ` Krzysztof Halasa
2007-06-01 22:17 ` H. Peter Anvin
2007-06-01 22:42 ` Krzysztof Halasa
2007-06-02 0:37 ` John Anthony Kazos Jr.
2007-06-02 0:56 ` Krzysztof Halasa [this message]
2007-06-02 1:36 ` Valdis.Kletnieks
2007-06-01 17:27 ` Valdis.Kletnieks
2007-06-01 17:35 ` Andrew Morton
2007-06-01 18:14 ` Dave Jones
2007-06-01 18:22 ` Andrew Morton
2007-06-01 18:28 ` Dave Jones
2007-06-02 17:17 ` Jan Engelhardt
2007-06-02 18:00 ` John Anthony Kazos Jr.
2007-06-02 19:07 ` Sam Ravnborg
2007-06-02 14:11 ` Adrian Bunk
2007-06-02 17:47 ` Andrew Morton
2007-06-02 17:55 ` Adrian Bunk
2007-06-03 0:23 ` Krzysztof Halasa
2007-06-03 2:57 ` Scott Preece
2007-06-03 4:06 ` Randy Dunlap
2007-06-03 4:15 ` Andrew Morton
2007-06-03 18:31 ` Scott Preece
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=m3lkf341j5.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jakj@j-a-k-j.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sepreece@gmail.com \
/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
Powered by JetHome