Rather than requiring users to have public remotes and private remotes when
their development remotes are ssh based (and therefor unsuitable for a pull
request URL), rewrite the ones we know about from ssh://git@ to git://.

With this infrastructure in place, future patches can augment the list of
known remotes for things like Git Hub, Gitorious, kernel.org, etc.

Signed-off-by: Darren Hart <[email protected]>
Cc: Tom Rini <[email protected]>
Cc: Martin Jansa <[email protected]>
Cc: Otavio Salvador <[email protected]>
Cc: Richard Purdie <[email protected]>
---
 scripts/create-pull-request |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/scripts/create-pull-request b/scripts/create-pull-request
index c6cf817..96cf04f 100755
--- a/scripts/create-pull-request
+++ b/scripts/create-pull-request
@@ -65,6 +65,16 @@ while getopts "b:hi:m:o:p:r:s:u:" OPT; do
                        echo "ERROR: git config failed to find a url for 
'$REMOTE'"
                        exit 1
                fi
+
+               # Rewrite known private URLs to public URLs
+               case "$REMOTE_URL" in
+               *ssh://[email protected]*)
+                       REMOTE_URL=${REMOTE_URL/'ssh://git@'/'git://'}
+                       ;;
+               *ssh://[email protected]*)
+                       REMOTE_URL=${REMOTE_URL/"ssh://git@"/"git://"}
+                       ;;
+               esac
                ;;
        esac
 done
-- 
1.7.1


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to