All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: linux-graphics-maintainer@vmware.com,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: vmwgfx GL3 and other -next (4.3) pathches
Date: Fri, 21 Aug 2015 16:43:55 +0200	[thread overview]
Message-ID: <55D7392B.5010207@vmware.com> (raw)
In-Reply-To: <55D7380C.3060902@gmail.com>

Hi

On 08/21/2015 04:39 PM, Emil Velikov wrote:
> On 21/08/15 13:42, Thomas Hellstrom wrote:
>> Unfortunately I wasn't aware that the mesa 11.0
>> branchpoint was immediately upcoming.
> It was mentioned on the mailing list (search for "release schedule")
> with a few reminders, plus a note in the #dri-devel IRC channel topic.
>
> If you can think of a way to make the process/timeline more obvious/well
> known, please let me know.
>

No. Entirely my fault. Been to busy with the kernel patches and other stuff.

Thanks,
Thomas
 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-08-21 14:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 18:31 vmwgfx GL3 and other -next (4.3) pathches Thomas Hellstrom
2015-08-12 21:02 ` Daniel Vetter
2015-08-13  5:06   ` Thomas Hellstrom
2015-08-12 21:07 ` Daniel Vetter
2015-08-13  5:04   ` Thomas Hellstrom
2015-08-13  6:38     ` Daniel Vetter
2015-08-13  7:18       ` Thomas Hellstrom
2015-08-14 11:29       ` Thomas Hellstrom
2015-08-21 12:31         ` Emil Velikov
2015-08-21 12:42           ` Thomas Hellstrom
2015-08-21 14:39             ` Emil Velikov
2015-08-21 14:43               ` Thomas Hellstrom [this message]
2015-08-21 14:51               ` Ilia Mirkin
2015-08-13 11:47 ` Emil Velikov
2015-08-13 12:07   ` Thomas Hellstrom

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=55D7392B.5010207@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=linux-graphics-maintainer@vmware.com \
    /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.