git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: lukaszgryglicki <lukaszgryglicki@o2.pl>
Cc: Dan Kohn <dan@linuxfoundation.org>, git@vger.kernel.org
Subject: Re: [PATCH v3] merge: add a --signoff flag.
Date: Wed, 26 Jul 2017 00:34:53 -0700	[thread overview]
Message-ID: <xmqqa83rtzvm.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <7A9ED766-4A25-4F34-8E02-3DFCE1D63ADF@o2.pl> (lukaszgryglicki@o2.pl's message of "Wed, 26 Jul 2017 09:13:57 +0200")

lukaszgryglicki <lukaszgryglicki@o2.pl> writes:

>>> +--signoff::
>>> +	Add Signed-off-by line by the committer at the end of the commit
>>> +	log message.  The meaning of a signoff depends on the project,
>>> +	but it typically certifies that committer has
>>> +	the rights to submit this work under the same license and
>>> +	agrees to a Developer Certificate of Origin
>>> +	(see http://developercertificate.org/ for more information).
>> 
>> This is taken verbatim from Documentation/git-commit.txt and "this
>> work" in that context is entirely sensible, but it is not quite
>> clear what it means in the context of "git merge”.
>
> Changed slightly, but I’m not a native English speaker, and
> don’t really see what is wrong there.

Oh, the language is not the issue.  

I was trying to remind you that a "merge" may be an automated and
mechanical one, in which there is no original work that requires
signing it off in the first place, which was the point Ævar raised
when Dan's original post came up.


  parent reply	other threads:[~2017-07-26  7:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  9:57 [PATCH] area: git-merge: add --signoff flag to git-merge Łukasz Gryglicki
2017-07-03 17:57 ` Junio C Hamano
2017-07-04  6:20 ` [PATCH v2] add --signoff flag to `git-merge` command Łukasz Gryglicki
2017-07-04  8:33   ` Ævar Arnfjörð Bjarmason
2017-07-04 17:42     ` Junio C Hamano
2017-07-04  9:33   ` [PATCH v3] merge: add a --signoff flag Łukasz Gryglicki
2017-07-24  6:14     ` lukaszgryglicki
2017-07-24  7:02       ` Junio C Hamano
2017-07-24 20:42         ` Junio C Hamano
2017-07-25  5:00           ` lukaszgryglicki
2017-07-25  5:10             ` Stefan Beller
2017-07-25 11:28           ` lukaszgryglicki
2017-07-25 18:41     ` Junio C Hamano
     [not found]       ` <7A9ED766-4A25-4F34-8E02-3DFCE1D63ADF@o2.pl>
2017-07-26  7:34         ` Junio C Hamano [this message]
2017-07-26  7:39     ` [PATCH v4] " Łukasz Gryglicki

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqa83rtzvm.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dan@linuxfoundation.org \
    --cc=git@vger.kernel.org \
    --cc=lukaszgryglicki@o2.pl \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).