From: David Kastrup <dak@gnu.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] blame.c: don't drop origin blobs as eagerly
Date: Sat, 28 May 2016 16:00:21 +0200 [thread overview]
Message-ID: <87bn3qnuyy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1605281430440.4449@virtualbox> (Johannes Schindelin's message of "Sat, 28 May 2016 14:34:35 +0200 (CEST)")
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi David,
>
> On Sat, 28 May 2016, David Kastrup wrote:
>
>> > The short version of your answer is that you will leave this patch in
>> > its current form and address none of my concerns because you moved on,
>> > correct? If so, that's totally okay, it just needs to be spelled out.
>>
>> Yes, that's it. You'll notice that the code change itself is both
>> minuscule as well purely functional, so it contains nothing
>> copyrightable.
>
> That is unfortunately an interpretation of the law that would need to
> come from a professional lawyer.
A professional lawyer would laugh at "Signed-off-by:" being of more
legal significance than a written record of intent but of course you
know that. This is mere bluster.
> As it is, the patch was clearly authored by you, and anybody else who
> would claim authorship would most likely be breaking the law.
The _diff_ is not "clearly authored" by me but just the simplest
expression of the intent. The commit message is clearly authored by me
but is not acceptable anyway. Whoever gets to write an acceptable
commit message is up for all copyrightable credit in my book. Feel free
to keep the authorship if you really want to, but when replacing the
commit message it is not a particularly accurate attribution.
> So I won't touch it.
Signed-off-by: David Kastrup <dak@gnu.org>
You don't get more than that for other patches either and it's a few
bytes compared to a mail conversation. Here is a PGP signature on top.
As I said: I am not going to put more work into it anyway and if it's an
occasion for theatralics, it has at least accomplished something.
--
David Kastrup
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2016-05-28 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 13:35 [PATCH] blame.c: don't drop origin blobs as eagerly David Kastrup
2016-05-27 15:00 ` Johannes Schindelin
2016-05-27 15:41 ` David Kastrup
2016-05-28 6:37 ` Johannes Schindelin
2016-05-28 8:29 ` David Kastrup
2016-05-28 12:34 ` Johannes Schindelin
2016-05-28 14:00 ` David Kastrup [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-02 11:56 David Kastrup
2019-04-03 7:45 ` Junio C Hamano
2019-04-03 9:32 ` Duy Nguyen
2019-04-03 11:36 ` Jeff King
2019-04-03 12:06 ` Duy Nguyen
2019-04-03 12:19 ` Jeff King
2019-04-03 12:32 ` David Kastrup
2019-04-03 11:08 ` David Kastrup
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=87bn3qnuyy.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.