From: Andreas Ericsson <ae@op5.se>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Tobias Toedter <t.toedter@gmx.net>, git@vger.kernel.org
Subject: Re: Question about commit message conventions
Date: Wed, 25 Oct 2006 17:23:51 +0200 [thread overview]
Message-ID: <453F8187.9060208@op5.se> (raw)
In-Reply-To: <20061024140856.GH5639@harddisk-recovery.com>
Erik Mouw wrote:
> On Tue, Oct 24, 2006 at 03:49:44PM +0200, Tobias Toedter wrote:
>
>> On the other hand, concerning the approval of other developers, what's the
>> difference between "Signed-off-by:" and "Acked-by:"? Are there any
>> more "*-by:" fields that are in use?
>
> Acked-by is usually used when someone (not the upstream maintainer the
> patch was send to) agrees with the patch. I.e.: (s)he says the content
> of the patch is OK without actually acknowledging something about the
> right to submit.
>
If you sift through the Linux kernel, you will find numerous patches
where subsystem maintainers have acked patches sent to them. I *think*
this usually means that they have reviewed the patch and approve of it,
but not modified it. The Ack is then solely for Linus' benefits and
tells him that at least one pair of eyes have already gone over the patch.
Subsys maintainers sometimes also add Signed-off-by: lines, which I
assume means they have tweaked the patch somewhat or somehow
collaborated with the author in producing it. I know Junio signs off
patches he modifies, and I'm guessing this habit is inherited from the
kernel workflow which was most likely encouraged by Linus when he was
the Git maintainer.
Lots of guesswork here, but in a sane world I can't be too far off the
mark ;-)
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
next prev parent reply other threads:[~2006-10-25 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 13:49 Question about commit message conventions Tobias Toedter
2006-10-24 14:08 ` Jakub Narebski
2006-10-24 14:14 ` Tobias Toedter
2006-10-24 14:08 ` Erik Mouw
2006-10-25 15:23 ` Andreas Ericsson [this message]
2006-10-25 18:48 ` Junio C Hamano
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=453F8187.9060208@op5.se \
--to=ae@op5.se \
--cc=erik@harddisk-recovery.com \
--cc=git@vger.kernel.org \
--cc=t.toedter@gmx.net \
/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).