path: root/t/
diff options
authorShawn O. Pearce <>2007-09-18 08:54:51 (GMT)
committerJunio C Hamano <>2007-09-19 10:22:31 (GMT)
commitd8b3a2bf189a9e7fea76454157b77fa71c9abc05 (patch)
tree66808d008034726076279f1ba8dae7ec95c2fad1 /t/
parent27e13374bf1864eb8aea44cca3afd81eedb007aa (diff)
Don't attempt to merge non-existant remotes in t5515
This was actually reverted in 756373da by Junio. We no longer support merging the right hand side of a fetchspec in a branch's branch.$name.merge configuration setting as we interpret these names as being only those published by the remote we are going to fetch from. The older shell based implementation of git-fetch did not report an error when branch.$name.merge was referencing a branch that does not exist on the remote and we are running `git fetch` for the current branch. The new builtin-fetch does notice this failure and aborts the fetch, thus breaking the tests. Junio and I kicked it around on #git earlier today and decided that the best approach here is to error out and tell the user that their configuration is wrong, as this is likely more user friendly than silently ignoring the user's request. Since the new builtin-fetch is already issuing the error there is no code change required, we just need to remove the bad configuration from our test. Signed-off-by: Shawn O. Pearce <>
Diffstat (limited to 't/')
1 files changed, 1 insertions, 2 deletions
diff --git a/t/ b/t/
index 6c9cc67..31c1081 100755
--- a/t/
+++ b/t/
@@ -84,8 +84,7 @@ test_expect_success setup '
git config$remote-merge.merge refs/heads/three &&
git config$remote-octopus.remote $remote &&
git config$remote-octopus.merge refs/heads/one &&
- git config --add$remote-octopus.merge two &&
- git config --add$remote-octopus.merge remotes/rem/three
+ git config --add$remote-octopus.merge two