From: Sven Guckes <guckes@math.fu-berlin.de>
To: ZSH Users <zsh-users@sunsite.auc.dk>
Subject: Re: Distribution Tar File Too Big - update?
Date: Wed, 8 Dec 1999 01:10:33 +0100 [thread overview]
Message-ID: <19991208011033.B215@ritz.math.fu-berlin.de> (raw)
In-Reply-To: <Pine.GSO.4.10.9911151402420.9831-100000@leeor.math.technion.ac.il>; from rl@math.technion.ac.il on Mon, Nov 15, 1999 at 02:19:27PM +0200
* Zvi Har'El <rl@math.technion.ac.il> [991115 12:19]:
> The distribution tar files of zsh since version
> 3.0.6 are twice as big as they should be. [...]
> The reason for that is when they generated, the
> tar script somehow included each file twice!
Has this been corrected yet?
Just curious as I did not
see any response to this...
Sven
prev parent reply other threads:[~1999-12-08 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 12:19 Distribution Tar File Too Big Zvi Har'El
1999-12-08 0:10 ` Sven Guckes [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19991208011033.B215@ritz.math.fu-berlin.de \
--to=guckes@math.fu-berlin.de \
--cc=zsh-users@sunsite.auc.dk \
/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).