All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: Question about commit message conventions
Date: Wed, 25 Oct 2006 11:48:58 -0700	[thread overview]
Message-ID: <7vbqo0b59h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <453F8187.9060208@op5.se> (Andreas Ericsson's message of "Wed, 25 Oct 2006 17:23:51 +0200")

Andreas Ericsson <ae@op5.se> writes:

> 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.

Correct.

> 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.
>...
> Lots of guesswork here, but in a sane world I can't be too far off the
> mark ;-)

Documentation/SubmittingPatches makes it unnecessary to make any
guesses on S-o-b lines.  Regarding subsystem maintainer
sign-offs, you are referring to DCO 1.1 (b), but the signature
could have been made under DCO 1.1 (c).

In plain terms, the signer vouches that the patch was passed
either intact or with modifications but the original and
modifications are both releasable, to the best of signer's
knowledge, under open source terms.


      reply	other threads:[~2006-10-25 18:49 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
2006-10-25 18:48     ` Junio C Hamano [this message]

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=7vbqo0b59h.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.