On 2014-01-31 14:04, David Kastrup wrote:
I'm still in the process of finishing the rewrite of the builtin/blame.c
internals. Now there are various questions regarding the final patch
proposals and commit messages.
Point 1) signing off implies that I'm fine with the licensing of the
Andreas Ericsson a...@op5.se writes:
On 2014-01-31 14:04, David Kastrup wrote:
I'm still in the process of finishing the rewrite of the builtin/blame.c
internals. Now there are various questions regarding the final patch
proposals and commit messages.
Point 1) signing off implies that
Hi,
David Kastrup wrote:
builtin/blame.c merely states
/*
* Blame
*
* Copyright (c) 2006, Junio C Hamano
*/
I think you planned to make substantial changes, so
/*
* Blame
*
* Copyright (c) 2006--2014, Junio C Hamano and others
* Licensed under GPLv2. See Git's
Jonathan Nieder jrnie...@gmail.com writes:
Also keep in mind that you don't need a copyright notice to own
copyright, that it would be crazy for someone to claim you've assigned
copyright on your changes without an explicit reassignment,
Not at all crazy: Documentation/SubmittingPatches
Hi,
David Kastrup wrote:
Also whether or not this implies an assignment of copyright, it is a
reasonable assumption for
[...]
Since I think we've completely gone off the rails:
I assume the problem you're trying to solve is that files don't have
clear enough notices of their licensing. That
Jonathan Nieder jrnie...@gmail.com writes:
I assume the problem you're trying to solve is that files don't have
clear enough notices of their licensing.
No, just the file that I'm contributing to. It has a single copyright
attribution that arguably is already less than accurate _unless_ the
: David Kastrup d...@gnu.org
To: Jonathan Nieder jrnie...@gmail.com
Cc: git@vger.kernel.org
Subject: Re: A few contributor's questions
Jonathan Nieder jrnie...@gmail.com writes:
I assume the problem you're trying to solve is that files don't have
clear enough notices of their licensing.
No, just
7 matches
Mail list logo