unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jeremy Bryant <jb@jeremybryant.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefankangas@gmail.com,  emacs-devel@gnu.org,
	Jonas Bernoulli <jonas@bernoul.li>
Subject: Re: magit copyright assignments
Date: Sat, 13 Jul 2024 22:39:29 +0100	[thread overview]
Message-ID: <87le25km3y.fsf@jeremybryant.net> (raw)
In-Reply-To: <86frsdjm20.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Jul 2024 19:25:59 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Jeremy Bryant <jb@jeremybryant.net>
>> Date: Sat, 13 Jul 2024 16:50:17 +0100
>> 
>> Stefan,
>> 
>> Following the recent commit in the etc/TODO for magit below.
>> 
>> '
>> *** Magit
>> This needs work on getting the relevant copyright assignments.  This
>> task should be highly doable for anyone, but will likely require some
>> patience.  For inspiration, see how this was done for 'use-package':
>> https://github.com/jwiegley/use-package/issues/282
>> '
>> 
>> Would you be able to confirm which contributors are missing assignments
>> on file?
>
> Quite a lot.  Do you need a full list?  Is it feasible to reach out to
> all of them?

I don't know how feasible this is (Jonas may know more on this), but
given the usefulness of magit, I can volunteer to start for some of this
task.

For this reason, yes I would like to see the full list of missings to
guide next steps.




  reply	other threads:[~2024-07-13 21:39 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 [this message]
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
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=87le25km3y.fsf@jeremybryant.net \
    --to=jb@jeremybryant.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jonas@bernoul.li \
    --cc=stefankangas@gmail.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. 
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).