From: Stefan Kangas <stefankangas@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: Replace 'pp' with 'prin1' to generate ELPA archive-contents
Date: Sat, 22 Oct 2022 04:56:47 -0700 [thread overview]
Message-ID: <CADwFkmmD107AfMj28JXAi1UU5JG5BQFfBm7HqS0SRx9AJW7X8Q@mail.gmail.com> (raw)
In-Reply-To: <87fsfgp1tx.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
> I've just tried replacing the 'pp' call with 'prin1' in elpa-admin's
> `elpaa-update-archive-contents', and on my checkout the size dropped
> from ~130 kb to 100 kb. It is not much, but I don't understand why the
> archive contents should be pretty printed, and even a few kilobyte less
> can make a difference for some people.
If we care about 30kb, how adding gzip support instead?
next prev parent reply other threads:[~2022-10-22 11:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 10:52 Replace 'pp' with 'prin1' to generate ELPA archive-contents Philip Kaludercic
2022-10-22 11:56 ` Stefan Kangas [this message]
2022-10-22 13:45 ` Philip Kaludercic
2022-10-22 15:01 ` Stefan Kangas
2022-10-22 15:33 ` Philip Kaludercic
2022-10-22 15:00 ` Stefan Monnier
2022-10-22 15:05 ` Philip Kaludercic
2022-10-25 19:28 ` Stefan Monnier
2022-10-26 6:43 ` Philip Kaludercic
2022-10-26 11:20 ` Eli Zaretskii
2022-10-26 11:39 ` Philip Kaludercic
2022-10-26 12:10 ` Stefan Monnier
2022-10-26 12:18 ` Eli Zaretskii
2022-10-26 14:11 ` Po Lu
2022-10-26 15:02 ` Stefan Monnier
2022-10-26 15:18 ` Robert Pluim
2022-10-26 15:25 ` Stefan Monnier
2022-10-26 15:31 ` Robert Pluim
2022-10-27 0:50 ` Po Lu
2022-10-27 8:33 ` Robert Pluim
2022-10-27 10:38 ` Po Lu
2022-10-27 11:40 ` Robert Pluim
2022-10-27 11:48 ` Po Lu
2022-10-27 0:49 ` Po Lu
2022-10-27 15:17 ` Stefan Monnier
2022-10-26 14:33 ` Stefan Kangas
2022-10-26 15:03 ` Stefan Monnier
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=CADwFkmmD107AfMj28JXAi1UU5JG5BQFfBm7HqS0SRx9AJW7X8Q@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).