From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 33880@debbugs.gnu.org
Subject: bug#33880: [PATCH] Compress past NEWS files during installation
Date: Thu, 14 Mar 2019 17:14:34 +0200 [thread overview]
Message-ID: <83zhpx1o9x.fsf@gnu.org> (raw)
In-Reply-To: <87a7hx7bcm.fsf@gmail.com> (message from Alex on Thu, 14 Mar 2019 08:57:13 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 14 Mar 2019 08:57:13 -0600
>
> agrambot@gmail.com writes:
>
> > This shaves off just over a MB off of the installation using gzip -9.
> > While I was at it, I put in the compression of etc/refcards/*.ps, which
> > covers part of a TODO.
> >
> > I wanted to compress etc/refcards/*.tex as well, but I noticed that it
> > would affect the Makefile that is also installed. It appears to be the
> > only Makefile that's installed; if there's little or no reason for it,
> > would it be okay to remove it during installation and compress the *.tex
> > files as well?
>
> Ping. Is this okay to apply to master?
Sorry for not responding earlier.
I don't think compressing *.ps files is a good idea, because then they
cannot be printed without manually uncompressing them.
As for NEWS, I don't have a strong opinion, but it sounds like a very
small gain for the trouble. What do others think? Perhaps this
should be discussed on emacs-devel first.
Thanks.
next prev parent reply other threads:[~2019-03-14 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 19:49 bug#33880: [PATCH] Compress past NEWS files during installation agrambot
2019-03-14 14:57 ` Alex
2019-03-14 15:14 ` Eli Zaretskii [this message]
2019-03-14 15:43 ` Alex
2019-03-14 15:54 ` Michael Albinus
2019-03-14 16:23 ` Alex
2019-03-14 17:59 ` Eli Zaretskii
2019-03-14 21:33 ` Alex
2019-03-14 22:00 ` Glenn Morris
2019-03-15 4:53 ` Eli Zaretskii
2019-03-16 18:28 ` Alex
2019-03-16 18:51 ` Eli Zaretskii
2019-03-16 20:08 ` Michael Albinus
2019-06-23 20:02 ` Lars Ingebrigtsen
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=83zhpx1o9x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33880@debbugs.gnu.org \
--cc=agrambot@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.