From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, Archit Taneja <architt@codeaurora.org>
Subject: [dim PATCH 0/2] dim fetch fixes
Date: Tue, 29 Nov 2016 18:17:14 +0200 [thread overview]
Message-ID: <cover.1480436023.git.jani.nikula@intel.com> (raw)
Fix a couple of issues that probably only plague setups that don't use
git-worktree.
We should probably consider adding Linus' tree and drm-tip to drm_tip_repos;
drm-tip is rebuilt based on drm_tip_config anyway. Anyway, this is the quick
fix.
BR,
Jani.
Jani Nikula (2):
dim: fetch Linus' tree again on update-branches
dim: fetch drm-tip before rebuilding
dim | 14 ++++++++++++++
1 file changed, 14 insertions(+)
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-11-29 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 16:17 Jani Nikula [this message]
2016-11-29 16:17 ` [dim PATCH 1/2] dim: fetch Linus' tree again on update-branches Jani Nikula
2016-11-30 10:48 ` Daniel Vetter
2016-11-29 16:17 ` [dim PATCH 2/2] dim: fetch drm-tip before rebuilding Jani Nikula
2016-11-30 10:48 ` 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=cover.1480436023.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=architt@codeaurora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).