From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: [PATCH 2/6] dim: don't check everything in dim setup
Date: Thu, 26 Jan 2017 10:10:45 +0100 [thread overview]
Message-ID: <20170126091049.9122-2-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20170126091049.9122-1-daniel.vetter@ffwll.ch>
Laurent got mightily confused about this, and assumed he's getting
volunteered as an intel maintainer because dim asks for an intel
remote.
With the branch autodetection we can postpone all the remote checks to
when we need them. This is similar to the changes to update-branches
to only update branches that exist, but for remotes.
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
dim | 7 -------
1 file changed, 7 deletions(-)
diff --git a/dim b/dim
index 5dfd0ef586be..e5afa9ee1bb8 100755
--- a/dim
+++ b/dim
@@ -1394,13 +1394,6 @@ function dim_setup
exit 1
fi
- cd $DIM_DRM_INTEL
-
- # check remote configuration
- remote=`url_to_remote $linux_upstream_git`
- remote=`url_to_remote $drm_intel_ssh`
- remote=`url_to_remote $drm_upstream_git`
-
cd $DIM_PREFIX
setup_aux_checkout maintainer-tools $drm_intel_ssh maintainer-tools
--
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-01-26 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 9:10 [PATCH 1/6] dim: Update docs Daniel Vetter
2017-01-26 9:10 ` Daniel Vetter [this message]
2017-01-26 9:10 ` [PATCH 3/6] dim: Also allow git urls Daniel Vetter
2017-01-26 10:39 ` Jani Nikula
2017-01-26 9:10 ` [PATCH 4/6] dim: Add git_is_current_branch helper Daniel Vetter
2017-01-26 10:43 ` Jani Nikula
2017-01-26 9:10 ` [PATCH 5/6] dim: Add helper for checking for a branch Daniel Vetter
2017-01-26 10:46 ` Jani Nikula
2017-01-26 9:10 ` [PATCH 6/6] dim: Don't try to create branches in update_branches Daniel Vetter
2017-01-26 10:47 ` Jani Nikula
2017-01-26 10:42 ` [PATCH] dim: Explain how to resolve conflicts when git rerere fails Daniel Vetter
2017-01-26 11:12 ` [PATCH 1/6] dim: Update docs Jani Nikula
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=20170126091049.9122-2-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@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.