{"thread":{"id":"6515","subject":"how to test changes?","startedAt":"2007-01-25T04:27:21Z","lastAt":"2007-01-25T05:57:50Z","messageCount":3,"participants":["Uwe Kleine-König","Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"32585","messageId":"20070125042721.GA6168@cepheus","threadId":"6515","inReplyTo":null,"subject":"how to test changes?","fromName":"Uwe Kleine-König","fromEmail":"ukleinek@informatik.uni-freiburg.de","sentAt":"2007-01-25T04:27:21Z","receivedAt":"2007-01-25T04:27:21Z","isPatch":false,"sender":{"key":"u.kleine-koenig@pengutronix.de","avatar":"https://gravatar.com/avatar/354b5e3ceb2806a2f1e1e382ac29ddbdad18288654da62b61eb13583a857eee7?d=mp&s=160"},"body":"Hello,\n\nI wonder if there is a simpler way to test changes to git than\ninstalling it.  My problem is that even if I run \n\n\t~/gsrc/git/git-fetch.sh --option\n\ne.g. git-parse-remote is taken from ~/usr/bin/git-parse-remote.\n\nDid I miss something?\n\nBest regards\nUwe\n\n-- \nUwe Kleine-König\n\nhttp://www.google.com/search?q=1+year+divided+by+3+in+seconds\n"},{"id":"32588","messageId":"20070125045730.GA20345@spearce.org","threadId":"6515","inReplyTo":"20070125042721.GA6168@cepheus","subject":"Re: how to test changes?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-01-25T04:57:30Z","receivedAt":"2007-01-25T04:57:30Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Uwe Kleine-K?nig <ukleinek@informatik.uni-freiburg.de> wrote:\n> I wonder if there is a simpler way to test changes to git than\n> installing it.  My problem is that even if I run \n\nLook at the INSTALL file:\n\n\tGIT_EXEC_PATH=`pwd`\n\tPATH=`pwd`:$PATH\n\tGITPERLLIB=`pwd`/perl/blib/lib\n\texport GIT_EXEC_PATH PATH GITPERLLIB\n\nI use this trick all of the time to run git in-place for testing\nin various weird repositories.\n\n-- \nShawn.\n"},{"id":"32590","messageId":"20070125055750.GA20545@cepheus","threadId":"6515","inReplyTo":"20070125045730.GA20345@spearce.org","subject":"[PATCH] untrue statement about git wrapper","fromName":"Uwe Kleine-König","fromEmail":"ukleinek@informatik.uni-freiburg.de","sentAt":"2007-01-25T05:57:50Z","receivedAt":"2007-01-25T05:57:50Z","isPatch":true,"sender":{"key":"u.kleine-koenig@pengutronix.de","avatar":"https://gravatar.com/avatar/354b5e3ceb2806a2f1e1e382ac29ddbdad18288654da62b61eb13583a857eee7?d=mp&s=160"},"body":"Hi Shawn\nShawn O. Pearce wrote:\n> Uwe Kleine-K?nig <ukleinek@informatik.uni-freiburg.de> wrote:\n> > I wonder if there is a simpler way to test changes to git than\n> > installing it.  My problem is that even if I run \n> \n> Look at the INSTALL file:\n> \n> \tGIT_EXEC_PATH=`pwd`\n> \tPATH=`pwd`:$PATH\n> \tGITPERLLIB=`pwd`/perl/blib/lib\n> \texport GIT_EXEC_PATH PATH GITPERLLIB\n> \nThanks, that's what I searched for.\n\nWhile reading INSTALL, I noticed the following\n\n-- >8 --\nDelete the now untrue statement that the git wrapper isn't used by the core\n\nSome time ago most (if not all) calls use the wrapper to allow moving some\ncommands from PATH to execdir.\n\nSigned-off-by: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>\n---\n INSTALL |    9 +++------\n 1 files changed, 3 insertions(+), 6 deletions(-)\n\ndiff --git a/INSTALL b/INSTALL\nindex 361c65b..66f64a6 100644\n--- a/INSTALL\n+++ b/INSTALL\n@@ -27,16 +27,13 @@ Issues of note:\n  - git normally installs a helper script wrapper called \"git\", which\n    conflicts with a similarly named \"GNU interactive tools\" program.\n \n-   Tough.  Either don't use the wrapper script, or delete the old GNU\n-   interactive tools.  None of the core git stuff needs the wrapper,\n-   it's just a convenient shorthand and while it is documented in some\n-   places, you can always replace \"git commit\" with \"git-commit\"\n-   instead. \n+   Tough.  \n \n    But let's face it, most of us don't have GNU interactive tools, and\n    even if we had it, we wouldn't know what it does.  I don't think it\n    has been actively developed since 1997, and people have moved over to\n-   graphical file managers.\n+   graphical file managers.  So I suggest to remove it from your system\n+   if you have it.\n \n  - You can use git after building but without installing if you\n    wanted to.  Various git commands need to find other git\n-- \n1.5.0.rc2.gd1af2d\n\n-- \nUwe Kleine-König\n\n$ dc -e \"5735816763073014741799356604682P\"\n"}]}