From: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
To: Dieter Mummenschanz <mummenschanz-hi6Y0CQ0nG0@public.gmane.org>
Cc: intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
libva-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [Intel-gfx] frequent x crashes with gen6/sna
Date: Mon, 17 Oct 2011 19:46:40 +0200 [thread overview]
Message-ID: <20111017174640.GI2971@phenom.ffwll.local> (raw)
In-Reply-To: <20111017160156.38210-hi6Y0CQ0nG0@public.gmane.org>
On Mon, Oct 17, 2011 at 06:01:56PM +0200, Dieter Mummenschanz wrote:
> Hi Daniel,
>
> ok I did a git clone git://anongit.freedesktop.org/libva (hope this is the right one?) and in the libva checkout I issued:
>
> git pull git://freedesktop.org/~danvet/libva-intel for-dieter
> warning: no common commits
> remote: Counting objects: 1632, done.
> remote: Compressing objects: 100% (447/447), done.
> remote: Total 1632 (delta 1174), reused 1632 (delta 1174)
> Receiving objects: 100% (1632/1632), 617.29 KiB | 230 KiB/s, done.
> Resolving deltas: 100% (1174/1174), done.
> From git://freedesktop.org/~danvet/libva-intel
> * branch for-dieter -> FETCH_HEAD
> Auto-merging configure.ac
> CONFLICT (add/add): Merge conflict in configure.ac
> Auto-merging Makefile.am
> CONFLICT (add/add): Merge conflict in Makefile.am
> Auto-merging .gitignore
> CONFLICT (add/add): Merge conflict in .gitignore
> Automatic merge failed; fix conflicts and then commit the result.
>
> help! :-(
Ok, I've given that git repo a head, so your usual git clone should work.
Btw, you're sure you have the latest libva? It moved to
http://cgit.freedesktop.org/vaapi/intel-driver/
Yours, Daniel
--
Daniel Vetter
Mail: daniel-/w4YWyX8dFk@public.gmane.org
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-10-17 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 12:37 frequent x crashes with gen6/sna Dieter Mummenschanz
[not found] ` <20111017123721.34230-hi6Y0CQ0nG0@public.gmane.org>
2011-10-17 13:16 ` [Intel-gfx] " Daniel Vetter
2011-10-17 13:54 ` Dieter Mummenschanz
[not found] ` <20111017135403.266530-hi6Y0CQ0nG0@public.gmane.org>
2011-10-17 14:50 ` [Intel-gfx] " Daniel Vetter
2011-10-17 15:13 ` Dieter Mummenschanz
2011-10-17 15:48 ` Daniel Vetter
2011-10-17 16:01 ` Dieter Mummenschanz
[not found] ` <20111017160156.38210-hi6Y0CQ0nG0@public.gmane.org>
2011-10-17 17:46 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 20:20 Dieter Mummenschanz
[not found] ` <20111017202009.183480-hi6Y0CQ0nG0@public.gmane.org>
2011-10-17 20:46 ` [Intel-gfx] " Daniel Vetter
[not found] ` <20111017204632.GL2971-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2011-10-18 7:52 ` Dieter Mummenschanz
2011-10-16 9:22 Dieter Mummenschanz
2011-10-16 16:18 ` Daniel Vetter
2011-10-17 11:45 ` Dieter Mummenschanz
2011-10-17 11:58 ` Daniel Vetter
[not found] ` <20111017115803.GC2971-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2011-10-17 12:13 ` [Intel-gfx] " Gwenole Beauchesne
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=20111017174640.GI2971@phenom.ffwll.local \
--to=daniel-/w4ywyx8dfk@public.gmane.org \
--cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=libva-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=mummenschanz-hi6Y0CQ0nG0@public.gmane.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