From 03215e336573a08c6169df835d80f182cb5b0bee Mon Sep 17 00:00:00 2001
From: Fathi Boudra <fathi.boudra@linaro.org>
Date: Tue, 7 Apr 2015 11:00:44 +0300
Subject: use the refs/heads/<branchName> syntax

<remoteRepoName>/<branchName> can be ambiguous.

Per the documentation:
The safest way is to use the refs/heads/<branchName> syntax.
This way the expected branch is unambiguous.

If ambiguous the first result is taken, which is not necessarily
the expected one. Better use refs/heads/<branchName>.

Change-Id: I838e2b22e3b256d1c294e8a071a97960f109e652
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
---
 coresight.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'coresight.yaml')

diff --git a/coresight.yaml b/coresight.yaml
index 37fcd2291b..0b89731609 100644
--- a/coresight.yaml
+++ b/coresight.yaml
@@ -24,7 +24,7 @@
             refspec: +refs/heads/master:refs/remotes/origin/master
             name: origin
             branches:
-                - origin/master
+                - refs/heads/master
             skip-tag: true
             shallow-clone: true
             wipe-workspace: false
-- 
cgit v1.2.3