zsh-workers
 help / color / mirror / code / Atom feed
From: Simon Ruderich <simon@ruderich.org>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Update FTP/HTTP mirrors.
Date: Sun, 17 Apr 2011 22:31:50 +0200	[thread overview]
Message-ID: <20110417203150.GA24304@ruderich.org> (raw)
In-Reply-To: <20110415161536.111330c0@pwslap01u.europe.root.pri>

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]

On Fri, Apr 15, 2011 at 04:15:36PM +0100, Peter Stephenson wrote:
> On Fri, 15 Apr 2011 16:46:11 +0200 Simon Ruderich wrote:
>> This patch updates the list of FTP/HTTP mirrors - most them are
>> either down or no longer contain the zsh sources.
>
> Thanks, please do submit it.

I don't have commit access (this patch is for the zsh
repository).

>> We should also update http://www.zsh.org/ which contains the same
>> dead links. The following files need to be regenerated for
>> http://zsh.sourceforge.net/ (I'm not sure how to do that):
>>
>>     - Doc/Release/Introduction.html
>>     - Doc/Release/zsh_2.html
>>
>>     - FAQ/META.html
>>     - FAQ/zshfaq01.html
>>     - FAQ/zshfaq.yo
>
> FAQ is made by "make" in the Etc directory of the distribution and the
> files are copied from there.  You can make an HTML version by "make
> FAQ.html".  It's got a different name from what's on the web --- I think
> that's just cosmetic.  It's amusing that the metafaq seems to have
> changed case in the opposite direction between the two.

Thanks. However my yodl version seems to be different (2.15.2 on
Debian Squeeze) and modifies the FAQ files in many places. Should
I just replace the old files or do you (or somebody else with the
correct yodl) want to generate the files?

I haven't found a way to generate META.html or
Doc/Release/zsh_2.html, any idea? The Doc/Release notes seem to
be quite outdated, should I update the rest as well?

>> Btw. do we really need the FTP mirrors in two places: Etc/FAQ.yo
>> and Doc/Zsh/metafaq.yo?
>
> No, that's historical.  FAQ.yo was a single standalone piece of text and
> metafaq.yo was included into the manual.

Any idea how to resolve that? Should we just keep it in two
places or remove it from one (which)?

Regards,
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-04-17 20:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 14:46 Simon Ruderich
2011-04-15 15:15 ` Peter Stephenson
2011-04-17 20:31   ` Simon Ruderich [this message]
2011-04-18 19:25     ` Peter Stephenson
2011-04-20  0:06       ` Simon Ruderich
2011-04-20  0:14         ` Simon Ruderich
2011-04-22 23:40         ` Wayne Davison
2011-04-25 13:14           ` Simon Ruderich
2011-04-25 16:24             ` Wayne Davison
2011-04-25 19:22               ` Simon Ruderich
2011-04-30 18:46         ` Peter Stephenson

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=20110417203150.GA24304@ruderich.org \
    --to=simon@ruderich.org \
    --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).