From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lele@metapensiero.it, emacs-devel@gnu.org
Subject: Re: magit copyright assignments
Date: Sat, 20 Jul 2024 23:00:20 -0400 [thread overview]
Message-ID: <E1sVMo8-0002pw-CA@fencepost.gnu.org> (raw)
In-Reply-To: <86wmljffga.fsf@gnu.org> (message from Eli Zaretskii on Thu, 18 Jul 2024 08:15:49 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > > What about the other case: you contributed some code, but later all of
> > > that was deleted?
> >
> > In this case, there is no need for this contributor to submit papers.
> Which means "git annotate" actually _is_ the right way, at least part
> of it. The question is where to start and how to converge between
> these two.
In the case where someone's past contribution was all deleed, `git
annotate' would show a sign of that. But its results can be misleading
in some other cases.
Consider another case: someone did minor edits on all the lines of that
past contribution. In that case, none of the contributed lines
would survive unchnged, but most of the material of the contribution
would remain.
Thus, one you see that someone made enough contribution to matter,
you need to check the code to see if that contribution is still present
in modified form.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-07-21 3:00 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1sVMo8-0002pw-CA@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.