From: Joseph Turner <joseph@ushin.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Emacs Devel Mailing List <emacs-devel@gnu.org>
Subject: Re: Why is the latest hyperdrive.el tarball so large?
Date: Wed, 25 Dec 2024 01:58:28 -0800 [thread overview]
Message-ID: <87h66sozi3.fsf@ushin.org> (raw)
In-Reply-To: <877c7qz1qm.fsf@igel.home> (Andreas Schwab's message of "Mon, 23 Dec 2024 19:35:29 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Dez 23 2024, Joseph Turner wrote:
>
>> Why is the latest tarball so much larger?
>
> It's uncompressed.
Thank you! That's obvious now that I see it.
Joseph
prev parent reply other threads:[~2024-12-25 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 18:04 Why is the latest hyperdrive.el tarball so large? Joseph Turner
2024-12-23 18:35 ` Andreas Schwab
2024-12-25 9:58 ` Joseph Turner [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=87h66sozi3.fsf@ushin.org \
--to=joseph@ushin.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).