From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] untrue statement about git wrapper
Date: Thu, 25 Jan 2007 06:57:50 +0100 [thread overview]
Message-ID: <20070125055750.GA20545@cepheus> (raw)
In-Reply-To: <20070125045730.GA20345@spearce.org>
Hi Shawn
Shawn O. Pearce wrote:
> Uwe Kleine-K?nig <ukleinek@informatik.uni-freiburg.de> wrote:
> > I wonder if there is a simpler way to test changes to git than
> > installing it. My problem is that even if I run
>
> Look at the INSTALL file:
>
> GIT_EXEC_PATH=`pwd`
> PATH=`pwd`:$PATH
> GITPERLLIB=`pwd`/perl/blib/lib
> export GIT_EXEC_PATH PATH GITPERLLIB
>
Thanks, that's what I searched for.
While reading INSTALL, I noticed the following
-- >8 --
Delete the now untrue statement that the git wrapper isn't used by the core
Some time ago most (if not all) calls use the wrapper to allow moving some
commands from PATH to execdir.
Signed-off-by: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
---
INSTALL | 9 +++------
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/INSTALL b/INSTALL
index 361c65b..66f64a6 100644
--- a/INSTALL
+++ b/INSTALL
@@ -27,16 +27,13 @@ Issues of note:
- git normally installs a helper script wrapper called "git", which
conflicts with a similarly named "GNU interactive tools" program.
- Tough. Either don't use the wrapper script, or delete the old GNU
- interactive tools. None of the core git stuff needs the wrapper,
- it's just a convenient shorthand and while it is documented in some
- places, you can always replace "git commit" with "git-commit"
- instead.
+ Tough.
But let's face it, most of us don't have GNU interactive tools, and
even if we had it, we wouldn't know what it does. I don't think it
has been actively developed since 1997, and people have moved over to
- graphical file managers.
+ graphical file managers. So I suggest to remove it from your system
+ if you have it.
- You can use git after building but without installing if you
wanted to. Various git commands need to find other git
--
1.5.0.rc2.gd1af2d
--
Uwe Kleine-König
$ dc -e "5735816763073014741799356604682P"
prev parent reply other threads:[~2007-01-25 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 4:27 how to test changes? Uwe Kleine-König
2007-01-25 4:57 ` Shawn O. Pearce
2007-01-25 5:57 ` Uwe Kleine-König [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=20070125055750.GA20545@cepheus \
--to=ukleinek@informatik.uni-freiburg.de \
--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).