From: Duy Nguyen <pclouds@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Elmar Pruesse <p@ucdenver.edu>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Reducing git size by building libgit.so
Date: Wed, 12 Jun 2019 16:46:33 +0700 [thread overview]
Message-ID: <CACsJy8Ce9exNKEYojo8Uu6WjyjSGN2imO-8Z4cXa-FGkXs4GJQ@mail.gmail.com> (raw)
In-Reply-To: <87y32787k9.fsf@evledraar.gmail.com>
On Wed, Jun 12, 2019 at 4:42 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> I.e. we'd just have one git binary, everything else symlinking to that,
> and we'd route to the right program by inspecting argv, which we mostly
> do already.
If I remember correctly libcurl.so startup time was the reason it's
split out of "git" binary, so we can't just merge everything into one
(*). But yeah merging some back is not a bad idea.
(*) but maybe "git" binary has gotten much slower overall, or
libcurl.so much faster that it does not matter anymore. That problem
was like 10 years ago.
--
Duy
next prev parent reply other threads:[~2019-06-12 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 19:52 Reducing git size by building libgit.so Elmar Pruesse
2019-06-11 23:48 ` brian m. carlson
2019-06-12 9:29 ` Duy Nguyen
2019-06-12 13:57 ` Paul Smith
2019-06-12 23:31 ` brian m. carlson
2019-06-13 19:19 ` Johannes Sixt
2019-06-13 7:51 ` Johannes Schindelin
2019-06-13 17:28 ` Paul Smith
2019-06-13 18:23 ` Junio C Hamano
2019-06-12 9:41 ` Ævar Arnfjörð Bjarmason
2019-06-12 9:46 ` Duy Nguyen [this message]
2019-06-12 10:25 ` SZEDER Gábor
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8Ce9exNKEYojo8Uu6WjyjSGN2imO-8Z4cXa-FGkXs4GJQ@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=p@ucdenver.edu \
/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://80x24.org/mirrors/git.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).