all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefankangas@gmail.com>,
	 emacs-devel@gnu.org, relekarpayas@gmail.com
Subject: Re: Merging use-package before Emacs 29, hopefully
Date: Tue, 29 Nov 2022 09:43:33 -0800	[thread overview]
Message-ID: <m28rjtr70a.fsf@newartisans.com> (raw)
In-Reply-To: <83bkowwfn0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Nov 2022 17:12:19 +0200")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

>> - If yes, do we have a list of commits that need such marking? Or,
>> equivalently, the authors whose work we don't need assignments for?

> I hope John can answer that. Truth be told, this should have been taken care
> of before pushing the scratch branch to the Emacs repository.

There has been a lot of work done here, starting since 2015:

  https://github.com/jwiegley/use-package/issues/282

It's possible that new commits came in after these copyrights were tracked
down. This issue, over the course of a few years, resulted in many people
submitting forms to the FSF. Given how many contributors there have been, this
may be a continuing task up until the moment of inclusion. From this point
forward, though, I will be extremely conservative about accepting PRs until
they have been signed.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



      parent reply	other threads:[~2022-11-29 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 13:19 Merging use-package before Emacs 29, hopefully Stefan Kangas
2022-11-24 15:12 ` Eli Zaretskii
2022-11-26  9:05   ` Stefan Kangas
2022-11-29 17:43   ` John Wiegley [this message]

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=m28rjtr70a.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=relekarpayas@gmail.com \
    --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 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.