Junio C Hamano <junkio@xxxxxxx> writes:
> Yann Dirson <ydirson@xxxxxxxxxx> writes:
> ...
>> Since branch.*.merge accept local ref names, there is probably far
>> more to change that what I initially feared.
>
> If that is the case maybe we should fix branch.*.merge not to
> match the local tracking branch name. Matching it with local
> tracking branch name when the remote name does not match was
> werely a fallback to help broken configurations confused people
> might create by hand, and has never been the part of sane
> practice at all.
That is, I suspect that reverting 80c79776 would make things a
lot more consistent.
-- >8 --
[PATCH] Revert "Allow branch.*.merge to talk about remote tracking branches."
This reverts commit 80c797764a6b6a373f0f1f47d7f56b0d950418a9.
Back when I committed this, it seemed to be a good idea. People
who always use remote tracking branches can optionally use the
local name they happen to use to specify what to merge, which meant
that I did not have to teach them why we use the name at the remote
side every time they are confused.
But allowing it seems to break other people's scripts. The real
solution is not to allow more ways to express the same thing, but
to educate people to use the right syntax.
Signed-off-by: Junio C Hamano <junkio@xxxxxxx>
---
git-parse-remote.sh | 8 ++------
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/git-parse-remote.sh b/git-parse-remote.sh
index 3e783b7..5208ee6 100755
--- a/git-parse-remote.sh
+++ b/git-parse-remote.sh
@@ -174,12 +174,8 @@ canon_refs_list_for_fetch () {
else
for merge_branch in $merge_branches
do
- if test "$remote" = "$merge_branch" ||
- test "$local" = "$merge_branch"
- then
- dot_prefix=
- break
- fi
+ [ "$remote" = "$merge_branch" ] &&
+ dot_prefix= && break
done
fi
case "$remote" in
--
1.5.0.rc3.24.g2391
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html