From: Peter Clifton <pcjc2@cam.ac.uk>
To: Intel <intel-gfx@lists.freedesktop.org>
Subject: drm-intel-next forced update?
Date: Mon, 22 Nov 2010 17:13:21 +0000 [thread overview]
Message-ID: <1290446001.9163.0.camel@pcjc2lap> (raw)
Was this intentional?
+ a17577c...5f75377 drm-intel-next -> drm-intel/drm-intel-next (forced update)
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
next reply other threads:[~2010-11-22 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 17:13 Peter Clifton [this message]
2010-11-22 17:19 ` drm-intel-next forced update? Chris Wilson
2010-11-22 17:32 ` Peter Clifton
2010-11-22 17:41 ` Chris Wilson
2010-11-22 17:48 ` Peter Clifton
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=1290446001.9163.0.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--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