t9114.2: Don't use --track option against "svn-remote"-tracking branches
commit983b17d4bbedd426d4fdd8a95df4dcd292c1a695
authorJohan Herland <johan@herland.net>
Sun, 21 Apr 2013 21:52:04 +0000 (21 23:52 +0200)
committerJunio C Hamano <gitster@pobox.com>
Sun, 21 Apr 2013 22:14:41 +0000 (21 15:14 -0700)
treec82b5ef83e8873a3676ab5368aafbc72458b4a70
parent88a9f72fe0f2ae3243b3d7a53dddf856cde48aca
t9114.2: Don't use --track option against "svn-remote"-tracking branches

We are formalizing a requirement that any remote-tracking branch to be used
as an upstream (i.e. as an argument to --track), _must_ "belong" to a
configured remote by being matched by the "dst" side of a fetch refspec.

This test uses --track against a "remotes/trunk" ref which does not belong
to any configured (git) remotes, but is instead created by "git svn fetch"
operating on an svn-remote. It does not make sense to use an svn-remote as
an upstream for a local branch, as a regular "git pull" from (or "git push"
to) it would obviously fail (instead you would need to use "git svn" to
communicate with this remote). Furthermore, the usage of --track in this
case is unnecessary, since the upstreaming config that would be created is
never used.

Simply removing --track fixes the issue without changing the expected
behavior of the test.

Acked-by: Eric Wong <normalperson@yhbt.net>
Signed-off-by: Johan Herland <johan@herland.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t9114-git-svn-dcommit-merge.sh