From: Bart Schaefer <schaefer@brasslantern.com>
To: dana <dana@dana.is>
Cc: Marlon Richert <marlon.richert@gmail.com>,
"Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: install.info failure
Date: Sat, 5 Jun 2021 09:09:49 -0700 [thread overview]
Message-ID: <CAH+w=7Y6Mo0ZqV16HkRai5e=QaWAgiuBS9aRxsvEEz=sEd4tyw@mail.gmail.com> (raw)
In-Reply-To: <F23E55F0-18EA-453C-92DE-649435FBBE7D@dana.is>
On Fri, Jun 4, 2021 at 2:49 PM dana <dana@dana.is> wrote:
>
> On 2 Jun 2021, at 01:33, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > Anyone else care to comment on that?
>
> I'm not sure I understand the root issue here, but, just in terms of
> consistency with the rest of the documentation, neither of the proposed
> changes seem ideal, do they? I don't know enough about Yodl to know what else
> to do off the top of my head, though
Consistency with what was previously there would be to remove the
linked cross-reference and just make a plain-text reference to the
other section. All this stuff that Marlon is doing is adding to the
internal linkages, which is well-intentioned but unrelated to the
original change that created the build problem.
next prev parent reply other threads:[~2021-06-05 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 13:11 Vin Shelton
2021-05-22 13:23 ` Daniel Shahaf
2021-05-24 20:22 ` Daniel Shahaf
2021-05-25 4:00 ` Jun T
2021-05-25 6:48 ` Bart Schaefer
2021-05-25 8:25 ` Jun T
2021-05-25 16:00 ` Bart Schaefer
2021-05-25 16:47 ` Daniel Shahaf
2021-05-25 20:58 ` Marlon Richert
2021-05-25 21:54 ` Bart Schaefer
2021-05-25 22:16 ` dana
2021-05-27 18:26 ` Marlon Richert
2021-05-31 22:33 ` Bart Schaefer
2021-06-01 10:44 ` Marlon Richert
2021-06-02 6:33 ` Bart Schaefer
2021-06-04 21:49 ` dana
2021-06-05 16:09 ` Bart Schaefer [this message]
2021-06-13 18:23 ` [PATCH] " Bart Schaefer
2021-06-05 10:47 Thomas Paulsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7Y6Mo0ZqV16HkRai5e=QaWAgiuBS9aRxsvEEz=sEd4tyw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=dana@dana.is \
--cc=marlon.richert@gmail.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).