From: Stefan Kangas <stefan@marxist.se>
To: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
Cc: 37546@debbugs.gnu.org
Subject: bug#37546: 26.3; Implement multi-file package README long description generation as described by elisp manual
Date: Thu, 23 Jan 2020 23:21:56 +0100 [thread overview]
Message-ID: <871rrp95kr.fsf@marxist.se> (raw)
In-Reply-To: <87pnjfsyf8.fsf@oitofelix.com> ("Bruno Félix Rezende Ribeiro"'s message of "Tue, 01 Oct 2019 22:56:11 -0300")
Hi Bruno,
Bruno Félix Rezende Ribeiro <oitofelix@gnu.org> writes:
>> In there, we also consider other names for the README file. Could we
>> perhaps base ourselves on that code somehow?
>
> I think it’s a good idea to try to read all those READMEs in turn until
> the first one succeeds, like it’s done there. Are you proposing
> something deeper?
Did you get any further with this?
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-01-23 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 3:52 bug#37546: 26.3; Implement multi-file package README long description generation as described by elisp manual Bruno Félix Rezende Ribeiro
2019-09-30 17:35 ` Stefan Kangas
2019-10-02 1:56 ` Bruno Félix Rezende Ribeiro
2019-10-02 9:31 ` Stefan Kangas
2020-01-23 22:21 ` Stefan Kangas [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=871rrp95kr.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=37546@debbugs.gnu.org \
--cc=oitofelix@gnu.org \
/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).