From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
Philip Kaludercic <philipk@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 64985@debbugs.gnu.org
Subject: bug#64985: 29.1; [PATCH] Byte-compilation of packages via package-vc doesn't correctly handle .elpaignore wildcards
Date: Tue, 1 Aug 2023 12:22:56 -0700 [thread overview]
Message-ID: <fb6b9f2e-6084-045c-5077-752affb78533@gmail.com> (raw)
In-Reply-To: <83sf930zzc.fsf@gnu.org>
On 8/1/2023 4:21 AM, Eli Zaretskii wrote:
> Btw, do we have somewhere the documentation of all those features,
> including the .elpaignore file and what it can include? I don't see
> this documented anywhere, so it's a small wonder people make such
> mistakes (if they are mistakes).
I'll look into this. I was already looking for a good place to put the
documentation I had discussed on emacs-devel about how to choose a good
name for an ELPA package, so it would probably make sense for
documentation about .elpaignore to live alongside that.
next prev parent reply other threads:[~2023-08-01 19:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:20 bug#64985: 29.1; [PATCH] Byte-compilation of packages via package-vc doesn't correctly handle .elpaignore wildcards Jim Porter
2023-08-01 11:21 ` Eli Zaretskii
2023-08-01 19:22 ` Jim Porter [this message]
2023-08-01 12:20 ` Philip Kaludercic
2023-08-01 16:10 ` Jim Porter
2023-08-01 16:18 ` Jim Porter
2023-08-01 17:29 ` Mattias Engdegård
2023-08-01 18:10 ` Jim Porter
2023-08-01 18:32 ` Philip Kaludercic
2023-08-01 19:18 ` Jim Porter
2023-08-01 19:21 ` Philip Kaludercic
2023-08-02 18:08 ` Jim Porter
2023-08-04 19:37 ` bug#64985: 30.0.50; package-recompile-all and package-recompile do not recompile anything, seems related to the patch associated with bug #64985 Vincenzo Pupillo
2023-08-04 20:05 ` Jim Porter
2023-08-05 17:12 ` Mattias Engdegård
2023-08-05 17:16 ` Jim Porter
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=fb6b9f2e-6084-045c-5077-752affb78533@gmail.com \
--to=jporterbugs@gmail.com \
--cc=64985@debbugs.gnu.org \
--cc=eliz@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 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.