From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: philipk@posteo.net, monnier@iro.umontreal.ca, 65027@debbugs.gnu.org
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Fri, 04 Aug 2023 08:42:53 +0300 [thread overview]
Message-ID: <83il9vweg2.fsf@gnu.org> (raw)
In-Reply-To: <4cf2941f-299c-fdb6-e2f5-375e8fc4e8e0@gmail.com> (message from Jim Porter on Thu, 3 Aug 2023 15:02:12 -0700)
> Date: Thu, 3 Aug 2023 15:02:12 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, philipk@posteo.net, 65027@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> As a general guideline for documentation, I'm thinking that anything a
> package author puts in their own repository would get documented in the
> Emacs Lisp manual, whereas anything that goes in the (Non)GNU ELPA
> repository (e.g. in the elpa-packages file) goes in the ELPA README.
> That makes intuitive sense to me as a package author at least: then the
> Emacs Lisp manual would have everything I need to *prepare* my package
> for eventual inclusion in ELPA.
To have the best of both worlds, please have the ELisp manual mention
the ELPA README file, and ELPA README file to mention specific nodes
of the ELisp manual where this stuff is described.
next prev parent reply other threads:[~2023-08-04 5:42 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 [this message]
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
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=83il9vweg2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65027@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--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).