author | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 10 Feb 2010 02:01:29 +0000 (18:01 -0800) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 10 Feb 2010 03:25:36 +0000 (19:25 -0800) | ||
commit | 6b3fa7e7d13a3c8fddba43ad6e8acb314d1985ac | |
tree | b31293fda40b8b7fe6ed45566d231e2cdeead46d | tree | snapshot |
parent | 6d525d389fbef814b11e41f196e6656f2e95f412 | commit | diff |
t5401: Use a bare repository for the remote peer
We want to avoid the warnings (or later, test failures) about
updating the current branch. It was never my intention to have
this test deal with a repository with a working directory, and it
is a very old bug that the test even used a non-bare repository
for the remote side of the push operations.
This fixes the interleaved output error we were seeing as a test
failure by avoiding the giant warning message we were getting back
about updating the current branch being risky.
Its not a real fix, but is something we should do no matter what,
because the behavior will change in the future to reject, and the
test would break at that time.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We want to avoid the warnings (or later, test failures) about
updating the current branch. It was never my intention to have
this test deal with a repository with a working directory, and it
is a very old bug that the test even used a non-bare repository
for the remote side of the push operations.
This fixes the interleaved output error we were seeing as a test
failure by avoiding the giant warning message we were getting back
about updating the current branch being risky.
Its not a real fix, but is something we should do no matter what,
because the behavior will change in the future to reject, and the
test would break at that time.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t5401-update-hooks.sh | diff | blob | history |