From: "Shawn O. Pearce" <spearce@spearce.org>
To: Eygene Ryabinkin <rea-git@codelabs.ru>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Introduce file with the common default build-time items.
Date: Thu, 14 Jun 2007 00:36:33 -0400 [thread overview]
Message-ID: <20070614043633.GV6073@spearce.org> (raw)
In-Reply-To: <20070613054316.GN86872@void.codelabs.ru>
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. It appears inside of
git.git only as a convience for users. So I cannot reference
../common-make-vars.def as not all git-gui repositories have a
git.git repository wrapped around them.
--
Shawn.
next prev parent reply other threads:[~2007-06-14 4:36 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 [this message]
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
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=20070614043633.GV6073@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=rea-git@codelabs.ru \
/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).