Which version x.org xserver got rid of ClockRanges?
kevinbrace at gmx.com
Tue Feb 16 22:12:27 UTC 2016
Can I include your name in the commit I will put into OpenChrome shortly?
It will look like this.
Suggested-by: Pekka Paalanen <"Your e-mail">
Signed-off-by: Kevin Brace <kevinbrace at gmx.com>
Let me know if it is okay.
If you do not want your name included, I will remove it.
I will set XORG_VERSION_NUMERIC to (1,8,0,0,0), since I assume this means x.org xserver Version 1.08.
> Sent: Tuesday, February 16, 2016 at 4:00 AM
> From: xorg-devel-request at lists.x.org
> To: xorg-devel at lists.x.org
> Subject: xorg-devel Digest, Vol 85, Issue 42
> Message: 3
> Date: Tue, 16 Feb 2016 09:54:15 +0200
> From: Pekka Paalanen <ppaalanen at gmail.com>
> To: "Kevin Brace" <kevinbrace at gmx.com>
> Cc: xorg-devel at lists.x.org
> Subject: Re: Which version x.org xserver got rid of ClockRanges?
> Message-ID: <20160216095415.42a04178 at eldfell>
> Content-Type: text/plain; charset="utf-8"
> I'm no xserver developer, but this seems to be fairly easy to find out
> with git in an xserver checkout:
> $ git log -SClockRangesPtr --all
> brings up a list of commits, the first one of which is the one whose
> email you found:
> commit 326429badfc76885e4652ddc72860810c0e8d102
> Author: Adam Jackson <ajax at redhat.com>
> Date: Tue Nov 10 14:56:36 2009 -0500
> modes: Remove the ClockRanges type
> Then to find out about the versions, we can do:
> $ git describe 326429badfc76885e4652ddc72860810c0e8d102
> $ git describe --contains 326429badfc76885e4652ddc72860810c0e8d102
> So we see that this particular patch landed between release tags
> 18.104.22.168 and 22.214.171.1241.
> Hope that helps.
More information about the xorg-devel