From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [dim PATCH 3/6] dim: look at all tip branches in dim tc
Date: Tue, 3 Oct 2017 16:38:05 +0300 [thread overview]
Message-ID: <20171003133808.28680-4-jani.nikula@intel.com> (raw)
In-Reply-To: <20171003133808.28680-1-jani.nikula@intel.com>
The hard-coded list of remotes and branches has gone stale.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
dim | 25 ++++++++++++++++---------
1 file changed, 16 insertions(+), 9 deletions(-)
diff --git a/dim b/dim
index ae8f30b8db83..f2cc25fc4ce9 100755
--- a/dim
+++ b/dim
@@ -1953,7 +1953,7 @@ function dim_cat_to_fixup
function dim_tc
{
- local sha1 tag dim_drm_upstream_remote
+ local sha1 tag conf remote_branches
sha1=${1:?$usage}
@@ -1961,15 +1961,22 @@ function dim_tc
tag=$(git tag --contains $sha1 | grep ^v | sort -V | head -n 1)
if [[ -n "$tag" ]]; then
echo "$tag"
- else
- dim_drm_upstream_remote=$(url_to_remote $drm_upstream_git)
- # not in a tagged release, show upstream branches
- git branch -r --contains $sha1 \
- $DIM_DRM_INTEL_REMOTE/* \
- $dim_drm_upstream_remote/drm-next \
- $dim_drm_upstream_remote/drm-fixes \
- origin/master | sed 's/^ *//'
+ return 0
fi
+
+ # not in a tagged release, show upstream branches
+ remote_branches="origin/master"
+ for conf in "${drm_tip_config[@]}"; do
+ local repo branch override url_list remote
+
+ read -r repo branch override <<< $conf
+ url_list=${drm_tip_repos[$repo]}
+ remote=$(url_to_remote $url_list)
+
+ remote_branches="$remote_branches $remote/$branch"
+ done
+
+ git branch -r --contains $sha1 $remote_branches | sed 's/^ *//' | sort
}
function dim_cite
--
2.11.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-03 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 13:38 dim: some repo/remote refactoring Jani Nikula
2017-10-03 13:38 ` [dim PATCH 1/6] dim: require explicit repo in create-branch Jani Nikula
2017-10-03 13:38 ` [dim PATCH 2/6] dim: url_to_remote can't normally fail Jani Nikula
2017-10-03 15:17 ` Jani Nikula
2017-10-05 8:57 ` Jani Nikula
2017-10-05 17:05 ` Daniel Vetter
2017-10-06 8:54 ` Jani Nikula
2017-10-03 13:38 ` Jani Nikula [this message]
2017-10-03 13:38 ` [dim PATCH 4/6] dim: s/DIM_DRM_INTEL/DIM_REPO/ Jani Nikula
2017-10-03 13:38 ` [dim PATCH 5/6] dim: figure drm-intel remote out automatically Jani Nikula
2017-10-03 13:38 ` [dim PATCH 6/6] dim: reduce dependency on hard-coded repo URLs Jani Nikula
2017-10-05 17:08 ` Daniel Vetter
2017-10-05 8:53 ` [dim PATCH] dim: cd to dim repo in list-upstreams Jani Nikula
2017-10-05 17:09 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171003133808.28680-4-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.