From: Eygene Ryabinkin <rea-git@codelabs.ru>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [CORRECTED PATCH] Introduce file with the common default build-time items.
Date: Fri, 15 Jun 2007 09:40:02 +0400 [thread overview]
Message-ID: <20070615054002.GD3779@void.codelabs.ru> (raw)
In-Reply-To: <20070615032204.GC18491@spearce.org>
Shawn, good da.y
Thu, Jun 14, 2007 at 11:22:04PM -0400, Shawn O. Pearce wrote:
> > OK, it means that git-gui will be totally separated from the
> > git.git? And one will download it as the separate tarball?
>
> That's one option. But Junio and I are also considering keeping
> it inside the git tarball as well, as many users have gotten used
> to it being in the core Git distribution. I think it all depends
> on if myself (or someone else) adds subproject recursion support
> into git-archive. ;-)
OK, I just wondered what to expect from the 1.6, since I am
trying to keep FreeBSD port in sync with the latest Git release.
> ...
> > Makefile | 17 +++++++++++------
> > common-make-vars.def | 11 +++++++++++
> > configure.ac | 4 +++-
> > 3 files changed, 25 insertions(+), 7 deletions(-)
> > create mode 100644 common-make-vars.def
> ...
>
> I dunno. 25 insertions and 7 deletions to reduce two uses of 'wish'
> into one use of 'wish'? That hardly seems worth the additional
> 18 lines of code.
11 of new lines are common-make-vars.def: it is heavily commented.
> Feels like code churn to me. And I rarely feel
> code churn. I'm usually a lot more caviler about changing things
> than Junio, Dscho, Nico, Linus, ...
OK, let us wait for the other's reaction. May be you're right and
it doesn't worth it. But I always felt that if I can change something
by changing it only in one place, then it worth it. Otherwise I
should remember all places where it is used and this leads to errors.
But maybe the 'wish' and 'tclsh' are not worth it.
Thank you!
--
Eygene
next prev parent reply other threads:[~2007-06-15 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 5:43 [PATCH] Introduce file with the common default build-time items Eygene Ryabinkin
2007-06-14 4:36 ` Shawn O. Pearce
2007-06-14 9:56 ` Eygene Ryabinkin
2007-06-14 15:09 ` Shawn O. Pearce
2007-06-14 19:07 ` [CORRECTED PATCH] " Eygene Ryabinkin
2007-06-15 3:22 ` Shawn O. Pearce
2007-06-15 5:40 ` Eygene Ryabinkin [this message]
2007-06-15 5:58 ` Shawn O. Pearce
2007-06-15 6:07 ` Eygene Ryabinkin
2007-06-15 7:15 ` Johannes Sixt
2007-06-15 10:28 ` Eygene Ryabinkin
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=20070615054002.GD3779@void.codelabs.ru \
--to=rea-git@codelabs.ru \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).