all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, johnw@gnu.org, relekarpayas@gmail.com
Subject: Re: Merging use-package before Emacs 29, hopefully
Date: Sat, 26 Nov 2022 01:05:57 -0800	[thread overview]
Message-ID: <CADwFkm=-6txVrHTaty5pZvAEpOWoDGOPRTDzHvNpFQ-E938xbw@mail.gmail.com> (raw)
In-Reply-To: <83bkowwfn0.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> 2. I didn't mark trivial commits with "Copyright-paperwork-exempt: yes".
>>    Using the scripts from João and Payas, it will be trivial to add, if
>>    I can get access to a list of the relevant commits.
>>
>>    - Do we care strongly about this?
>
> Yes, we do.
>
>>    - 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.
>
>> 3. The mailmap.txt file may or may not need looking over.  For example,
>>    I'm not sure how important it is that the emails line up with the
>>    copyright assignments file.
>
> It is pretty important, so if there are significant discrepancies, we'd need
> that incorporated.

Thanks, I have emailed you privately about the above.

>> 5. I added the files README.md as admin/USE-PACKAGE.README and NEWS.md
>>    as etc/USE-PACKAGE-NEWS.  We might want to just skip these files
>>    though, as they don't add much.  They are available in the old
>>    repository if anyone should need to take a look at them.
>
> Why do we need the README?  Ideally, it should be incorporated into the
> manual, and then discarded.

Yup, so let's just skip it.  All relevant information from README.md
will be in the texinfo manual.

> As for USE-PACKAGE.NEWS, unless we are going to keep updating it, I would
> omit it as well.  If you "git rm" it, it will be in Git history if someone
> needs it.

Sounds good.



  reply	other threads:[~2022-11-26  9:05 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 [this message]
2022-11-29 17:43   ` John Wiegley

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='CADwFkm=-6txVrHTaty5pZvAEpOWoDGOPRTDzHvNpFQ-E938xbw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=relekarpayas@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.