From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Makefile: do not compile git with debugging symbols by default
Date: Thu, 22 Jan 2015 18:36:41 +0100 [thread overview]
Message-ID: <vpqa91ahg46.fsf@anie.imag.fr> (raw)
In-Reply-To: <CANCZXo7ocgG27Y48NjYxurVMWOvHkvGqDrLuntkSTxHUK6hcNw@mail.gmail.com> (Alexander Kuleshov's message of "Thu, 22 Jan 2015 22:51:55 +0600")
Alexander Kuleshov <kuleshovmail@gmail.com> writes:
> Hello Jeff,
>
> Yes, main point is size of executable.
The Git executable is a few megabytes, i.e. 0.001% the size of a really
small hard disk. The benefit seems really negligible to me.
OTOH, debug information allow users to do better bug reports in case of
crash (gdb, valgrind), which outweights by far the benefit of saving a
handfull of megabytes IMHO.
On a side note, I find it very frustrating when a program I use
crashes, opens a bug report wizard, and end up telling me "sorry, your
distro removed the debug symbols, recompile everything if you want to
report a bug".
I understand that for a few users, the size of executable matters. But
this category of users should be able to find the "strip" target or
something equivalent.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-01-22 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 12:50 [PATCH] Makefile: do not compile git with debugging symbols by default Alexander Kuleshov
2015-01-22 13:00 ` Jeff King
2015-01-22 15:09 ` Mike Hommey
2015-01-22 16:51 ` Alexander Kuleshov
2015-01-22 16:53 ` Alexander Kuleshov
2015-01-22 17:36 ` Matthieu Moy [this message]
2015-01-22 18:35 ` Jeff King
2015-01-22 22:55 ` Mike Hommey
2015-01-27 8:43 ` David Aguilar
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=vpqa91ahg46.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kuleshovmail@gmail.com \
--cc=peff@peff.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.
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.