From: A Large Angry SCM <gitzilla@gmail.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] make git installation footprint smaller
Date: Fri, 23 Jul 2010 14:12:20 -0400 [thread overview]
Message-ID: <4C49DB84.9060001@gmail.com> (raw)
In-Reply-To: <taBDPvzBKDtgdmYKlcbFJ_fQRnY4jBMR74BF1vetbRU3OZRMPpwtU0wTG1SSa0hFgNsCN5k9Qx8@cipher.nrlssc.navy.mil>
On 07/23/2010 01:50 PM, Brandon Casey wrote:
> Ever wonder where that extra 5MB of disk space went that you thought you
> had? Well, it turns out that git isn't being quite as space-efficient as
> it could be. Some files that could be installed as links are instead being
> installed as full copies of the original.
>
> With these two patches, we shrink the installation footprint of git by
> making hard or symbolic links for non-builtin programs and for those binaries
> installed in the bin directory. We already do this for binaries installed
> in libexec. This can reduce the size of a git installation on the order of
> 10-30%. Probably about 5-10MB. Whoopee!!!
>
> Enjoy.
>
> Brandon Casey (2):
> Makefile: link builtins residing in bin directory to main git binary
> too
> Makefile: make hard/symbolic links for non-builtins too
>
> Makefile | 15 ++++++++++++---
> 1 files changed, 12 insertions(+), 3 deletions(-)
>
What happens when bindir and execdir are the same?
next prev parent reply other threads:[~2010-07-23 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 17:50 [PATCH 0/2] make git installation footprint smaller Brandon Casey
2010-07-23 17:50 ` [PATCH 1/2] Makefile: link builtins residing in bin directory to main git binary too Brandon Casey
2010-07-23 17:50 ` [PATCH 2/2] Makefile: make hard/symbolic links for non-builtins too Brandon Casey
2010-07-23 18:12 ` A Large Angry SCM [this message]
2010-07-23 18:17 ` [PATCH 0/2] make git installation footprint smaller Brandon Casey
2010-07-24 2:31 ` Jonathan Nieder
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=4C49DB84.9060001@gmail.com \
--to=gitzilla@gmail.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.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.
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).