From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
No Wayman <iarchivedmywholelife@gmail.com>,
62856@debbugs.gnu.org
Subject: bug#62856: 30.0.50; nongnu.git documentation out of date
Date: Tue, 05 Sep 2023 18:08:58 -0400 [thread overview]
Message-ID: <jwvpm2wgtse.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmmLLz2TQcysWPA7FVL9Skvc7ZBBRkH5OJ63UEZ1qfHkPQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 5 Sep 2023 14:36:20 -0700")
Stefan Kangas [2023-09-05 14:36:20] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Not much to add: the README in `elpa-admin` is supposed to be "generic"
>> (under the assumption that `elpa-admin` could be used for many other
>> archives), whereas the READMEs in the `main` branch of `elpa.git` and
>> `nongnu.git` should describe what's specific to the corresponding
>> (Non)GNU ELPA case and delegate the rest to the `elpa-admin` README.
> So notabug, then,
On the contrary: the README for nongnu.git should be fixed so it doesn't
say "externals/.." since that doesn't apply to the `nongnu.git` case.
> or do you see anything that could be improved?
Actually, a lot could be improved. What I describe above is what we aim
for, but the reality is pretty far from that: we managed to "merge" the
different redundant pieces of info (at some point, at least), which was
the first step, but we still need to split them according to
the guidelines which should then make it easier to keep those things
up-to-date.
Stefan
prev parent reply other threads:[~2023-09-05 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 7:29 bug#62856: 30.0.50; nongnu.git documentation out of date No Wayman
2023-04-15 13:09 ` Philip Kaludercic
2023-09-05 20:50 ` Stefan Kangas
2023-09-05 21:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 21:36 ` Stefan Kangas
2023-09-05 22:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=jwvpm2wgtse.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=62856@debbugs.gnu.org \
--cc=iarchivedmywholelife@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).