From: Eygene Ryabinkin <rea-git@codelabs.ru>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Introduce file with the common default build-time items.
Date: Thu, 14 Jun 2007 13:56:54 +0400 [thread overview]
Message-ID: <20070614095654.GT86872@void.codelabs.ru> (raw)
In-Reply-To: <20070614043633.GV6073@spearce.org>
Shawn, good day.
Thu, Jun 14, 2007 at 12:36:33AM -0400, Shawn O. Pearce wrote:
> Eygene Ryabinkin <rea-git@codelabs.ru> wrote:
> > Words 'wish' and 'tclsh' are scattered across at least three files,
> > but they are tied to the same entities. To ease the maintenance
> > and remove errors, these configuration items were gathered into the
> > separate file named 'common-make-vars.def'.
> ...
> > diff --git a/git-gui/Makefile b/git-gui/Makefile
> > index 3de0de1..654641a 100644
> > --- a/git-gui/Makefile
> > +++ b/git-gui/Makefile
> > @@ -6,6 +6,8 @@ all::
> > GIT-VERSION-FILE: .FORCE-GIT-VERSION-FILE
> > @$(SHELL_PATH) ./GIT-VERSION-GEN
> > -include GIT-VERSION-FILE
> > +# Default values
> > +-include ../common-make-vars.def
>
> A good idea to try and make these all common, but you cannot do this,
> or at least this part of the patch.
>
> The git-gui subdirectory of git.git is actually its own project,
> maintained in its own Git repository.
OK, but then may be it will be logical to put Tcl/Tk-related variables
to the git-gui/common-make-vars.def? I am a little worried about
this, because gitk is the part of the git.git and it should get the
variables too. The drawback here is if you will update your git-gui
repo, then git.git will need to wait for your import to get the
changes in the variables. And this will seriously couple git.git
and git-gui, though I don't know if it is good or bad.
Any ideas?
--
Eygene
next prev parent reply other threads:[~2007-06-14 9:57 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 [this message]
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
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=20070614095654.GT86872@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).