| commit | 9b092f9892e89d943197991fd813657e03a8acc7 | |
| author | Joshua Roys <roysjosh@gmail.com> | |
| Fri, 8 Aug 2008 20:37:23 +0000 (8 16:37 -0400) | ||
| committer | Sam Vilain <sam@vilain.net> | |
| Sun, 10 Aug 2008 16:54:57 +0000 (11 04:54 +1200) | ||
| tree | 1960d0b28f1dc1fba536689b917dfdc431f8742f | treesnapshot (tar.gz zip) |
| parent | 49c63639e4b5bc5147aa926c3c881ceec7d492e5 | commitdiff |
Workaround for bug (feature?) in Git::command_bidi_pipe
command_bidi_pipe doesn't make provision for the case where the git repo is
not in the current working directory. Unlike the other forms of passing
commands to Git.pm, it does not set GIT_DIR or chdir into the working
directory. The functions in Git.pm that rely on command_bidi_pipe also have
this problem.
Also, Git->repository doesn't like being passed a relative path. Git.pm's
_cmd_exec sets GIT_DIR to the relative path and then chdir's into the repo.
Now it tries to access the relative path from inside the repo. Boom.
[change not applicable to this branch, but test changes carried over
- SamV]
command_bidi_pipe doesn't make provision for the case where the git repo is
not in the current working directory. Unlike the other forms of passing
commands to Git.pm, it does not set GIT_DIR or chdir into the working
directory. The functions in Git.pm that rely on command_bidi_pipe also have
this problem.
Also, Git->repository doesn't like being passed a relative path. Git.pm's
_cmd_exec sets GIT_DIR to the relative path and then chdir's into the repo.
Now it tries to access the relative path from inside the repo. Boom.
[change not applicable to this branch, but test changes carried over
- SamV]
| t/52-pwp-references.t | diffblobblamehistory |