From: "Shawn O. Pearce" <spearce@spearce•org>
To: "Uwe Kleine-König" <ukleinek@informatik•uni-freiburg.de>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: how to test changes?
Date: Wed, 24 Jan 2007 23:57:30 -0500 [thread overview]
Message-ID: <20070125045730.GA20345@spearce.org> (raw)
In-Reply-To: <20070125042721.GA6168@cepheus>
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
I use this trick all of the time to run git in-place for testing
in various weird repositories.
--
Shawn.
next prev parent reply other threads:[~2007-01-25 4:57 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 [this message]
2007-01-25 5:57 ` [PATCH] untrue statement about git wrapper Uwe Kleine-König
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=20070125045730.GA20345@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=ukleinek@informatik$(echo .)uni-freiburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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