Re: [PATCH] fix git-parse-remote.sh for remotes that contain slashes

Stefan Naewe [off-list ref] writes:

Signed-off-by: Stefan Naewe <redacted>
---

Thanks, but no explanation?

Imagine somebody who weren't reading this thread (especially the article
you responded to with this patch) sees this in "git log" output stream.
For that matter, imagine yourself doing that in 2012 when the motivation
of this change you all forgot already.

Do you think it is obvious what the problem the patch tried to fix was?
I don't.  "fix" on the subject line gives you 0-bit information for that
purpose.

I suspect that making this case arm trigger not on */* but only on /* and
../* would be a lot more sensible solution.  Otherwise you would still
have the same issue in repositories that use remotes/ and branches/
mechanism.

 git-parse-remote.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/git-parse-remote.sh b/git-parse-remote.sh
index 1cc2ba6..8ec33e3 100644
--- a/git-parse-remote.sh
+++ b/git-parse-remote.sh

@@ -6,7 +6,7 @@ GIT_DIR=$(git rev-parse -q --git-dir) || :;
 
 get_data_source () {
 	case "$1" in
-	*/*)
+	../* | /*)
 		echo ''
 		;;
 	.)