All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Tobias Toedter <t.toedter@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: Question about commit message conventions
Date: Tue, 24 Oct 2006 16:08:56 +0200	[thread overview]
Message-ID: <20061024140856.GH5639@harddisk-recovery.com> (raw)
In-Reply-To: <200610241549.48238.t.toedter@gmx.net>

On Tue, Oct 24, 2006 at 03:49:44PM +0200, Tobias Toedter wrote:
> although I've read the documentation of git very carefully, I could not find 
> anything related to certain commit message conventions. It would be great 
> if someone here could explain a few things, maybe this could be added to 
> the wiki afterwards (<http://git.or.cz/gitwiki/CommitMessageConventions>).
> 
> First of all, what's the intended use of the "Signed-off-by:" lines? Does it 
> make sense to add my name there, even when I'm listed as the author or 
> committer of a commit? I thought that they are intended mostly to note the 
> approval of other developers.

See Documentation/SubmittingPatches. You basically say you have the
right to submit the patch.

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


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  parent reply	other threads:[~2006-10-24 14:09 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 [this message]
2006-10-25 15:23   ` Andreas Ericsson
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=20061024140856.GH5639@harddisk-recovery.com \
    --to=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 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.