| commit | d8b3a2bf189a9e7fea76454157b77fa71c9abc05 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 18 Sep 2007 08:54:51 +0000 (18 04:54 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 19 Sep 2007 10:22:31 +0000 (19 03:22 -0700) | ||
| tree | 66808d008034726076279f1ba8dae7ec95c2fad1 | treesnapshot (tar.gz zip) |
| parent | 27e13374bf1864eb8aea44cca3afd81eedb007aa | commitdiff |
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 <spearce@spearce.org>
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 <spearce@spearce.org>
| t/t5515-fetch-merge-logic.sh | diffblobblamehistory |