From: Stefan Kangas <stefan@marxist.se>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3
Date: Sun, 2 Jan 2022 11:00:26 -0500 [thread overview]
Message-ID: <CADwFkmkp6fe0rtQUOJP7s3OoOzu3_bF17+QiqoJCBc-NCGewyQ@mail.gmail.com> (raw)
In-Reply-To: <87ilv2s6bc.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
> And while we are at it, is there a reason not to add a MELPA-like
> keyword to manually specify what files are part of a package? Whenever
> a single repository is used to maintain multiple packages (like Magit or
> Embark) there is always a long list of :ignored-files that have to be
> duplicated for every package. Perhaps a more general version of
> .elpaignore could be used to declare packages externally.
Both of these ideas sounds good to me.
next prev parent reply other threads:[~2022-01-02 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164107430330.17202.17260845381664886032@vcs2.savannah.gnu.org>
[not found] ` <20220101215824.BB13CC0DEC3@vcs2.savannah.gnu.org>
2022-01-01 23:03 ` [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3 Stefan Monnier
2022-01-01 23:47 ` Stefan Kangas
2022-01-02 0:02 ` Stefan Kangas
2022-01-02 11:52 ` Philip Kaludercic
2022-01-02 16:00 ` Stefan Kangas [this message]
2022-01-02 20:12 ` Stefan Monnier
2022-01-03 8:41 ` Stefan Kangas
2022-01-03 15:46 ` Stefan Monnier
2022-01-03 4:37 ` Richard Stallman
2022-01-03 8:20 ` Philip Kaludercic
2022-01-04 3:09 ` Richard Stallman
2022-01-02 20:02 ` Stefan Monnier
2022-01-02 20:24 ` Stefan Kangas
2022-01-02 20:31 ` Stefan Monnier
2022-01-04 4:04 ` Stefan Kangas
2022-01-04 6:04 ` Stefan Monnier
2022-01-02 0:16 ` Stefan Monnier
2022-01-02 1:34 ` Stefan Kangas
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=CADwFkmkp6fe0rtQUOJP7s3OoOzu3_bF17+QiqoJCBc-NCGewyQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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).