From: Eygene Ryabinkin <rea-git@codelabs.ru>
To: Johannes Sixt <J.Sixt@eudaptics.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [CORRECTED PATCH] Introduce file with the common default build-time items.
Date: Fri, 15 Jun 2007 14:28:48 +0400 [thread overview]
Message-ID: <20070615102847.GF3779@void.codelabs.ru> (raw)
In-Reply-To: <46723C9F.4EE044F9@eudaptics.com>
Johannes, good day.
Fri, Jun 15, 2007 at 09:15:43AM +0200, Johannes Sixt wrote:
> Eygene Ryabinkin wrote:
> > 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.
>
> Huh? This "one place" already exists. Its name is 'config.mak'. I have
> this in it:
>
> TCL_PATH=tclsh84
> TCLTK_PATH=wish84
config.mak is a bit different: it is not used by the configure when
it sets the default TCL_PATH. But ok, I feel that my change is not
very good, since two of you already disliked it. Please, don't
waste your time on it anymore.
--
Eygene
prev parent reply other threads:[~2007-06-15 10:28 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
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 [this message]
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=20070615102847.GF3779@void.codelabs.ru \
--to=rea-git@codelabs.ru \
--cc=J.Sixt@eudaptics.com \
--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).