unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: philipk@posteo.net, 65027@debbugs.gnu.org, info@protesilaos.com,
	corwin@bru.st, stefankangas@gmail.com, monnier@iro.umontreal.ca
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Sun, 28 Jan 2024 07:46:59 +0200	[thread overview]
Message-ID: <86ede26mcs.fsf@gnu.org> (raw)
In-Reply-To: <c913437a-e14a-9486-7a4d-36181230323f@gmail.com> (message from Jim Porter on Sat, 27 Jan 2024 12:34:17 -0800)

> Cc: philipk@posteo.net, corwin@bru.st, monnier@iro.umontreal.ca,
>  info@protesilaos.com, 65027@debbugs.gnu.org
> Date: Sat, 27 Jan 2024 12:34:17 -0800
> From: Jim Porter <jporterbugs@gmail.com>
> 
> On 1/11/2024 11:35 AM, Jim Porter wrote:
> > On 1/10/2024 1:49 PM, Stefan Kangas wrote:
> >> But while we wait for that work to complete, is there any reason not to
> >> install the below patch?  Because we currently don't have any
> >> documentation for .elpaignore, and it's kind of frustrating to have to
> >> tell people that it exists over and over.
> >>
> >> Thoughts/objections?  Thanks in advance.
> > 
> > Makes sense to me. If others agree, I can merge my patch.
> 
> Since no one has had any further comments in the last couple weeks, I've 
> now merged my patch to master as 744a10a4d72.

Thanks, I fixed it slightly.

Btw, it is a bit strange in my eyes that this chapter talks about
package organization conventions on ELPA without ever mentioning that
those conventions are specific for ELPA, nor even describing what ELPA
is until a later section.  Perhaps the organization of the chapter
should be rethought, given that it no longer describes only
package.el, but also the conventions and requirements for submitting
packages to ELPA.





  parent reply	other threads:[~2024-01-28  5:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  4:56 bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual Jim Porter
2023-08-03  9:02 ` Eli Zaretskii
2023-08-03 13:36   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 17:24     ` Jim Porter
2023-08-03 19:09       ` Philip Kaludercic
2023-08-03 21:21       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 22:02         ` Jim Porter
2023-08-03 22:41           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-04  3:11             ` Jim Porter
2023-09-03 11:18               ` Stefan Kangas
2023-09-06  1:56                 ` Jim Porter
2023-09-06  2:22                   ` Corwin Brust
2023-09-19 13:29                     ` Corwin Brust
2023-09-19 13:53                       ` Protesilaos Stavrou
2023-09-20 10:35                   ` Protesilaos Stavrou
2023-09-21  1:37                     ` Stefan Kangas
2023-08-04  5:42           ` Eli Zaretskii
2023-08-05  1:58       ` Richard Stallman
2023-08-05  2:36         ` Corwin Brust
2023-08-05  6:03           ` Jim Porter
2023-08-05  6:45           ` Eli Zaretskii
2023-08-05 13:17           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-05  6:43         ` Eli Zaretskii
2024-01-10 21:49 ` Stefan Kangas
2024-01-11 19:35   ` Jim Porter
2024-01-27 20:34     ` Jim Porter
2024-01-28  2:42       ` Stefan Kangas
2024-01-28  5:46       ` Eli Zaretskii [this message]
2024-01-28  5:49         ` Stefan Kangas
2024-01-28  7:08           ` Eli Zaretskii
     [not found]   ` <87v8802yrp.fsf@protesilaos.com>
2024-01-11 19:38     ` 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=86ede26mcs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65027@debbugs.gnu.org \
    --cc=corwin@bru.st \
    --cc=info@protesilaos.com \
    --cc=jporterbugs@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --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).