From: Jeff King <peff@peff.net>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Nathaniel P Dawson <nathaniel.dawson@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org
Subject: Re: [PATCH 0/5] Header includes cleanup
Date: Fri, 3 Apr 2009 08:24:01 -0400 [thread overview]
Message-ID: <20090403122401.GA21153@coredump.intra.peff.net> (raw)
In-Reply-To: <200904030614.26310.chriscool@tuxfamily.org>
On Fri, Apr 03, 2009 at 06:14:26AM +0200, Christian Couder wrote:
> > So I don't know if it is worth it.
>
> I am not sure what you are talking about here, but if you mean that you
> don't think it's worth splitting gigantic .h files (like cache.h) into
> smaller logical units, then I agree.
What I meant was "there is a tradeoff between faster compilation times
and potentially more programmer effort, and I don't know if that
tradeoff is worth it". So I think you understood what I was saying, and
I think your point is reasonable.
-Peff
next prev parent reply other threads:[~2009-04-03 12:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 9:55 [PATCH 0/5] Header includes cleanup Nathaniel P Dawson
2009-03-30 9:55 ` [PATCH 1/5] " Nathaniel P Dawson
2009-03-30 9:55 ` [PATCH 2/5] " Nathaniel P Dawson
2009-03-30 9:55 ` [PATCH 3/5] " Nathaniel P Dawson
2009-03-30 9:55 ` [PATCH 4/5] " Nathaniel P Dawson
2009-03-30 9:55 ` [PATCH 5/5] " Nathaniel P Dawson
2009-03-30 10:50 ` [PATCH 0/5] " Johannes Sixt
2009-03-30 17:33 ` Nathaniel P Dawson
2009-03-31 6:59 ` Christian Couder
2009-03-31 16:04 ` Junio C Hamano
2009-04-02 3:57 ` Christian Couder
2009-04-02 5:25 ` Junio C Hamano
2009-04-02 11:27 ` Jeff King
2009-04-03 4:14 ` Christian Couder
2009-04-03 12:24 ` Jeff King [this message]
2009-04-03 3:58 ` Christian Couder
2009-03-31 5:53 ` Christian Couder
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=20090403122401.GA21153@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=nathaniel.dawson@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).