On Fri, 18 Dec 2015 12:26:53 -0600
Derek Foreman wrote:
> Just a quick ping on this because conversation has died down and nobody
> actually gave a RB or any suggestions for change.
>
> Someone flagged the patch as RFC in patchwork so it disappeared and I'm
> wondering if people may have thought
On Thu, 12 Nov 2015 14:01:33 -0600
Derek Foreman wrote:
> From: Jason Ekstrand
>
> This provides a standardized mechanism for tracking protocol object
> versions in client code. The wl_display object is created with version 1.
> Every time an object is created from within wl_registry_bind, it
Just a quick ping on this because conversation has died down and nobody
actually gave a RB or any suggestions for change.
Someone flagged the patch as RFC in patchwork so it disappeared and I'm
wondering if people may have thought it landed...
Where are we at with this?
I got Jason's RB on my tr
On Dec 7, 2015 7:20 AM, "Pekka Paalanen" wrote:
>
> On Wed, 25 Nov 2015 10:25:42 -0800
> Jason Ekstrand wrote:
>
> > On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman
wrote:
> > > On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> > >> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo <
giuliocamu...@gma
On Wed, 25 Nov 2015 10:25:42 -0800
Jason Ekstrand wrote:
> On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman
> wrote:
> > On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> >> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
> >> wrote:
> >>> So do i understand correctly that if the app creating
On Nov 25, 2015 12:03 PM, "Derek Foreman" wrote:
>
> On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> > On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
wrote:
> >> So do i understand correctly that if the app creating the
> >> wl_compositor was built against a libwayland without this patch the
> >>
On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
> wrote:
>> So do i understand correctly that if the app creating the
>> wl_compositor was built against a libwayland without this patch the
>> version returned in mesa by wl_proxy_get_version() for ever
On 25/11/15 12:25 PM, Jason Ekstrand wrote:
> On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman
> wrote:
>> On 13/11/15 12:21 PM, Jason Ekstrand wrote:
>>> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
>>> wrote:
So do i understand correctly that if the app creating the
wl_compositor
On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman wrote:
> On 13/11/15 12:21 PM, Jason Ekstrand wrote:
>> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
>> wrote:
>>> So do i understand correctly that if the app creating the
>>> wl_compositor was built against a libwayland without this patch the
On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
> wrote:
>> So do i understand correctly that if the app creating the
>> wl_compositor was built against a libwayland without this patch the
>> version returned in mesa by wl_proxy_get_version() for ever
On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo wrote:
> So do i understand correctly that if the app creating the
> wl_compositor was built against a libwayland without this patch the
> version returned in mesa by wl_proxy_get_version() for every proxy
> will be always 1?
Yes, see also the secon
So do i understand correctly that if the app creating the
wl_compositor was built against a libwayland without this patch the
version returned in mesa by wl_proxy_get_version() for every proxy
will be always 1?
2015-11-12 22:01 GMT+02:00 Derek Foreman :
> From: Jason Ekstrand
>
> This provides a
From: Jason Ekstrand
This provides a standardized mechanism for tracking protocol object
versions in client code. The wl_display object is created with version 1.
Every time an object is created from within wl_registry_bind, it gets the
bound version. Every other time an object is created, it s
13 matches
Mail list logo
