From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Robert Schiele <rschiele@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] add definitions for global variables to shell.c
Date: Tue, 19 Aug 2008 10:49:53 +0200 [thread overview]
Message-ID: <48AA8931.1030009@viscovery.net> (raw)
In-Reply-To: <7vpro5fnke.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> Even if that is the case, I do not like the prospect of having to maintain
> a set of duplicated variable definitions. If we really wanted to address
> this issue, maybe we would want a separate source file that is linked to
> both git-shell and to the rest of the system that has nothing but
> definitions of these variables? I thought environment.c was meant to be
> something like that -- would linking environment.o pull in too many extra
> references these days (again, I didn't try)?
Why not just revert 5b8e6f85f (shrink git-shell)? It was a nice try. If it
had not proved as a maintainance burden, it would have had merits. But who
these days cares whether git-shell takes 300K or 30K in the light of that
it goes out of the way anyway by execing some other process at the first
opportunity?
-- Hannes
next prev parent reply other threads:[~2008-08-19 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 12:37 [PATCH] add definitions for global variables to shell.c Robert Schiele
2008-08-19 0:29 ` Junio C Hamano
2008-08-19 7:26 ` Robert Schiele
2008-08-19 7:53 ` Junio C Hamano
2008-08-19 8:16 ` Robert Schiele
2008-08-19 8:49 ` Johannes Sixt [this message]
2008-08-19 9:18 ` Robert Schiele
2008-08-19 23:09 ` Junio C Hamano
2008-08-20 1:06 ` [PATCH 1/2] shell: do not play duplicated definition games to shrink the executable Junio C Hamano
2008-08-20 1:06 ` [PATCH 2/2] Build-in "git-shell" Junio C Hamano
2008-08-20 6:54 ` Johannes Sixt
2008-08-20 1:06 ` [PATCH] add definitions for global variables to shell.c Junio C Hamano
2008-08-20 4:36 ` Robert Schiele
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=48AA8931.1030009@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rschiele@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.
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).