From: Jonathan Nieder <jrnieder@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 21:31:45 -0500 [thread overview]
Message-ID: <20100724023145.GH13670@burratino> (raw)
In-Reply-To: <taBDPvzBKDtgdmYKlcbFJ_fQRnY4jBMR74BF1vetbRU3OZRMPpwtU0wTG1SSa0hFgNsCN5k9Qx8@cipher.nrlssc.navy.mil>
Brandon Casey wrote:
> Brandon Casey (2):
> Makefile: link builtins residing in bin directory to main git binary
> too
> Makefile: make hard/symbolic links for non-builtins too
So in the end, the hardlink-forming step has four steps:
1. (if bindir != libexecdir and NO_CROSS_DIRECTORY_HARDLINKS is unset)
Files in libexecdir with cousins in bindir are replaced by
hardlinks to their cousins. (patch 2)
2. Any builtins in bindir are replaced by
hardlinks, symlinks, or copies of git.
3. Any builtins in libexecdir are replaced by
hardlinks, symlinks, or copies of git.
4. git-remote-{ftp,http, etc} are replaced by
hardlinks, symlinks, or of git-remote-http.
Looks good to me.
Thanks for the pleasant read,
Jonathan
prev parent reply other threads:[~2010-07-24 2:32 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 ` [PATCH 0/2] make git installation footprint smaller A Large Angry SCM
2010-07-23 18:17 ` Brandon Casey
2010-07-24 2:31 ` Jonathan Nieder [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=20100724023145.GH13670@burratino \
--to=jrnieder@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).