From: dana <firstname.lastname@example.org> To: "Daniel Shahaf" <email@example.com> Cc: "Zsh hackers list" <firstname.lastname@example.org> Subject: Re: Posted zsh 5.9 Date: Sun, 15 May 2022 16:43:54 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <20220515103625.GC14994@tarpaulin.shahaf.local2> On Sun 15 May 2022, at 05:36, Daniel Shahaf wrote: > I don't understand the problem, since they'd _anyway_ have to get both > archives if they want to have HTML/PDF/info docs in --HEAD builds As far as i understand it, at least in principle: Bottle builds require both source and documentation archives because the shell itself is built from the source archive. In --HEAD builds the shell is built from VCS, so they would have no need for the source archive if not for the fact that some of the documentation happens to exist only there and not in the documentation one In practice i think they might be downloading one or both of the archives *anyway* just because they're defined in the formula. I'll look into it more and come back here if needed once i know what i'm talking about --- Anyway, i have posted the release announcement to -announce now. It's awaiting moderation dana
next prev parent reply other threads:[~2022-05-15 21:45 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-14 20:59 dana 2022-05-14 21:50 ` Daniel Shahaf 2022-05-14 21:58 ` Daniel Shahaf 2022-05-14 22:27 ` dana 2022-05-14 23:26 ` Daniel Shahaf 2022-05-14 23:28 ` Daniel Shahaf 2022-05-14 23:50 ` dana 2022-05-15 10:36 ` Daniel Shahaf 2022-05-15 21:43 ` dana [this message] 2022-05-16 23:57 ` Phil Pennock 2022-05-21 1:31 ` Daniel Shahaf 2022-05-14 22:11 ` Axel Beckert 2022-05-14 22:31 ` dana 2022-05-15 4:33 ` Bart Schaefer 2022-05-15 6:00 ` dana 2022-05-14 23:21 ` Daniel Shahaf 2022-05-14 23:35 ` Axel Beckert 2022-05-14 23:49 ` Daniel Shahaf
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Posted zsh 5.9' \ /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
Code repositories for project(s) associated with this 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).