From: Adrian Bunk <bunk@stusta.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Markus Dahms <dahms@fh-brandenburg.de>
Subject: Re: remove broken URLs from net drivers' output
Date: Thu, 10 May 2007 06:47:59 +0200 [thread overview]
Message-ID: <20070510044759.GG23574@stusta.de> (raw)
In-Reply-To: <46429E23.6050404@garzik.org>
On Thu, May 10, 2007 at 12:22:59AM -0400, Jeff Garzik wrote:
> Adrian Bunk wrote:
>> I thought it was just an informal tag to mark which people did agree with
>> the patch (and the line between your "Makes good sense to me." and a "Feel
>> free to add my ACK to this" is really thin).
>
> No, the line is easy and obvious: if there is any doubt, DO NOT ASSUME.
>
> If they do not explicitly ACK it, then do not presume to speak for them.
There is no doubt that Jesper did explicitly ACK the patch.
We are ONLY discussing whether his informal ACK can be translated into
an "Acked-by:" line.
The line I mentioned only exists if "Acked-by:" is considered a formal
tag someone must explicitely give, and not an informal indication that
someone agrees with the patch. But in this case, we should better
require people to give explicit "Acked-by:" lines, like we already
require for "Signed-off-by:" lines.
I've seen many cases where people other than me added "Acked-by:" tags
when there was only a "Makes good sense to me." or "Fine with me.", but
no formal "Acked-by:" given.
If "Acked-by:" should be considered a formal tag, it
- should be documented in Documentation/SubmittingPatches and
- the practice must change to always require people to give
a formal "Acked-by:".
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-05-10 4:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705092102.l49L2Re6028694@hera.kernel.org>
2007-05-09 22:41 ` remove broken URLs from net drivers' output Jeff Garzik
2007-05-09 23:04 ` Jesper Juhl
2007-05-10 4:07 ` Adrian Bunk
2007-05-10 4:22 ` Jeff Garzik
2007-05-10 4:47 ` Adrian Bunk [this message]
2007-05-10 9:44 ` Jesper Juhl
2007-05-10 3:57 ` Adrian Bunk
2007-05-10 4:23 ` Jeff Garzik
2007-05-10 4:58 ` Adrian Bunk
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=20070510044759.GG23574@stusta.de \
--to=bunk@stusta.de \
--cc=dahms@fh-brandenburg.de \
--cc=jeff@garzik.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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