# how to test changes? 3 messages from 2007-01-25 to 2007-01-25. Participants: Uwe Kleine-König, Shawn O. Pearce. Thread: https://gitlist.dev/t/6515 ## Uwe Kleine-König, 2007-01-25 04:27 Subject: how to test changes? Message-ID: <20070125042721.GA6168@cepheus> URL: https://gitlist.dev/e/20070125042721.GA6168%40cepheus ``` Hello, I wonder if there is a simpler way to test changes to git than installing it. My problem is that even if I run ~/gsrc/git/git-fetch.sh --option e.g. git-parse-remote is taken from ~/usr/bin/git-parse-remote. Did I miss something? Best regards Uwe -- Uwe Kleine-König http://www.google.com/search?q=1+year+divided+by+3+in+seconds ``` ## Shawn O. Pearce, 2007-01-25 04:57 Subject: Re: how to test changes? Message-ID: <20070125045730.GA20345@spearce.org> URL: https://gitlist.dev/e/20070125045730.GA20345%40spearce.org In-Reply-To: <20070125042721.GA6168@cepheus> ``` Uwe Kleine-K?nig 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 I use this trick all of the time to run git in-place for testing in various weird repositories. -- Shawn. ``` ## Uwe Kleine-König, 2007-01-25 05:57 Subject: [PATCH] untrue statement about git wrapper Message-ID: <20070125055750.GA20545@cepheus> URL: https://gitlist.dev/e/20070125055750.GA20545%40cepheus In-Reply-To: <20070125045730.GA20345@spearce.org> ``` Hi Shawn Shawn O. Pearce wrote: > Uwe Kleine-K?nig 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 --- 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" ```