From: Eli Zaretskii <eliz@gnu.org>
To: Lele Gaifax <lele@metapensiero.it>
Cc: emacs-devel@gnu.org
Subject: Re: magit copyright assignments
Date: Tue, 16 Jul 2024 21:25:03 +0300 [thread overview]
Message-ID: <86le21gpog.fsf@gnu.org> (raw)
In-Reply-To: <87ikx5s12c.fsf@metapensiero.it> (message from Lele Gaifax on Tue, 16 Jul 2024 19:23:39 +0200)
> From: Lele Gaifax <lele@metapensiero.it>
> Date: Tue, 16 Jul 2024 19:23:39 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, but I think "git annotate" or "C-x v g" will be much more
> > useful in this case, since we are only interested in how many lines
> > which are currently in the package a given author is responsible for.
>
> It's your call of course, but it seems strange to me: say I contributed
> 20 lines of code some time ago, and in the meantime someone edited it
> slightly, splitting it, moving it around, changing indentation... "git
> annotate" will say that most of my lines of code "belong" to someone
> else, but does that really matter in the context of copyright
> assignment? I'd say that I had still contributed those 20 lines of code,
> and thus I should sign the assignment paper, shouldn't I?
What about the other case: you contributed some code, but later all of
that was deleted?
I agree that some forensics and maybe "C-x v h" will be needed, but my
point is that git-commit-metrics is not necessarily the right starting
point, because it could easily show you a very distorted picture.
next prev parent reply other threads:[~2024-07-16 18:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 15:50 magit copyright assignments Jeremy Bryant
2024-07-13 16:25 ` Eli Zaretskii
2024-07-13 21:39 ` Jeremy Bryant
2024-07-14 4:50 ` Eli Zaretskii
2024-07-15 20:10 ` Jeremy Bryant
2024-07-15 20:49 ` Stefan Kangas
2024-07-16 2:17 ` Richard Stallman
2024-07-16 5:53 ` Lele Gaifax
2024-07-16 10:29 ` Eli Zaretskii
2024-07-16 17:23 ` Lele Gaifax
2024-07-16 18:25 ` Eli Zaretskii [this message]
2024-07-16 19:09 ` Lele Gaifax
2024-07-18 3:21 ` Richard Stallman
2024-07-18 5:15 ` Eli Zaretskii
2024-07-21 3:00 ` Richard Stallman
2024-07-16 2:18 ` Richard Stallman
2024-07-16 21:27 ` Jeremy Bryant
2024-07-17 11:23 ` Eli Zaretskii
2024-07-17 13:53 ` Jeremy Bryant
2024-07-18 3:21 ` Richard Stallman
2024-07-18 14:02 ` Jeremy Bryant
2024-07-18 15:31 ` Eli Zaretskii
2024-07-18 16:53 ` Jeremy Bryant
2024-07-18 17:40 ` Eli Zaretskii
2024-07-18 20:36 ` Jeremy Bryant
2024-07-19 17:32 ` Eli Zaretskii
2024-07-21 3:02 ` Richard Stallman
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86le21gpog.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lele@metapensiero.it \
/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://git.savannah.gnu.org/cgit/emacs.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).