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 17:29:40 -0400 [thread overview]
Message-ID: <jwvil8oia4y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmkwh-30fxRLJay4uVL+ju1jDNktYN5=nDm63MHJmtEwtg@mail.gmail.com> (Stefan Kangas's message of "Tue, 5 Sep 2023 13:50:59 -0700")
>>> nongnu.git's README and elpa-packages file claim each package will be
>>> on an "externals/NAME" branch. Instead the packages are on "elpa/NAME"
>>> branches.
>>
>> I am not exactly sure what is going on here, but the README file on the
>> elpa-admin branch mentions this:
>>
>> This file exists in two branches ~elpa-admin~ and ~elpa~. The two version
>> differ slightly. The introductory text before the first heading
>> differs and there are minor differences concerning the ~externals/*~ to
>> ~elpa/*~ transition. Please make sure you always update this file in
>> both locations to avoid introducing additional differences. This
>> duplication will be removed eventually.
>>
>>
>>> The elpa-config file implies this will be configurable at
>>> some point, but for now the docs are misleading.
>>
>> It should be configurable? Or at least `elpaa-read-config' does set it.
>
> Stefan, do you have any comments here?
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.
Stefan
next prev parent reply other threads:[~2023-09-05 21:29 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 [this message]
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
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=jwvil8oia4y.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).