Sebastien Bacher wrote:
> could you give the url to an upstream cairo discussion? there is no
> reason why we should ship distribution changes there which have not been
> discussed upstream, that creates extra work, bugs and political issues
>
This has been discussed several times, the last time here:
The amount of work this should cause is minimal, as it's normal
procedure to maintain a few patches. In the unlikely event that this
might cause a bugs, it's easy to have the offending driver fall back to
software. There is certainly no potential for this to cause political
issues.
Sebastien Bacher wrote:
> could you give the url to an upstream cairo discussion? there is no
> reason why we should ship distribution changes there which have not been
> discussed upstream, that creates extra work, bugs and political issues
>
This has been discussed several times, the last time here:
http:// lists.cairograp hics.org/ archives/ cairo/2009- January/ 016320. html
Carl has stated that he intends to use XRender for PAD/EXTEND_ REFLECT eventually, see here:
EXTEND_
http:// cgit.freedeskto p.org/xorg/ driver/ xf86-video- intel/commit/ ?id=128223ee9b7 880e64005647546 2eca9a88415492
The amount of work this should cause is minimal, as it's normal
procedure to maintain a few patches. In the unlikely event that this
might cause a bugs, it's easy to have the offending driver fall back to
software. There is certainly no potential for this to cause political
issues.