OpenBSD X11 changes summary for 2017-07-09 to 2017-07-16 inclusive
==================================================================

3RDPARTY                                app
xserver                                 

== 3RDPARTY ========================================================== 01/03 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/3RDPARTY

3RDPARTY


  > update (matthieu@)


  > update (matthieu@)

== app =============================================================== 02/03 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/app

app

  ~ cwm/kbfunc.c                          

  > Replace fgetln(3) with POSIX getline(3); inspired by brynet and Ingo.
  > feedback and ok brynet@ (okan@)

  ~ cwm/calmwm.h                          ~ cwm/conf.c
  ~ cwm/kbfunc.c                          

  > rename one function, matching others, to help upcoming change (okan@)

  - cwm/mousefunc.c                       ~ cwm/Makefile
  ~ cwm/calmwm.h                          ~ cwm/conf.c
  ~ cwm/kbfunc.c                          

  > Pull over the remaining re-implemented window move/resize functions and
  > create
  > a wrapper so that the key and mouse based move/resize callbacks can be
  > unified.
  > This has already been done with other window operations and menus. (okan@)

  ~ cwm/kbfunc.c                          

  > remove extra parentheses (okan@)

  ~ xterm/MANIFEST                        ~ xterm/NEWS
  ~ xterm/THANKS                          ~ xterm/Tekproc.c
  ~ xterm/XTerm.ad                        ~ xterm/button.c
  ~ xterm/cachedGCs.c                     ~ xterm/charclass.c
  ~ xterm/charclass.h                     ~ xterm/charproc.c
  ~ xterm/configure.in                    ~ xterm/ctlseqs.ms
  ~ xterm/ctlseqs.txt                     ~ xterm/cursor.c
  ~ xterm/data.h                          ~ xterm/doublechr.c
  ~ xterm/fontutils.c                     ~ xterm/fontutils.h
  ~ xterm/graphics.c                      ~ xterm/graphics_regis.c
  ~ xterm/html.c                          ~ xterm/input.c
  ~ xterm/main.c                          ~ xterm/main.h
  ~ xterm/menu.c                          ~ xterm/menu.h
  ~ xterm/minstall.in                     ~ xterm/misc.c
  ~ xterm/print.c                         ~ xterm/ptydata.c
  ~ xterm/ptyx.h                          ~ xterm/resize.c
  ~ xterm/screen.c                        ~ xterm/terminfo
  ~ xterm/trace.c                         ~ xterm/trace.h
  ~ xterm/util.c                          ~ xterm/version.c
  ~ xterm/version.h                       ~ xterm/wcwidth.c
  ~ xterm/wcwidth.h                       ~ xterm/xstrings.c
  ~ xterm/xstrings.h                      ~ xterm/xterm.h
  ~ xterm/xterm.log.html                  ~ xterm/xterm.man
  ~ xterm/xterm_io.h                      ~ xterm/xtermcfg.h
  ~ xterm/xtermcfg.hin                    ~ xterm/xutf8.c
  ~ xterm/package/xterm.spec              ~ xterm/package/debian/changelog
  ~ xterm/package/debian/control          ~ xterm/package/debian/copyright
  ~ xterm/package/debian/rules            ~ xterm/package/debian/xterm-dev.docs
  ~ xterm/package/debian/xterm-dev.menu   ~ xterm/package/freebsd/Makefile
  ~ xterm/vttests/256colors.pl            ~ xterm/vttests/256colors2.pl
  ~ xterm/vttests/88colors.pl             ~ xterm/vttests/88colors2.pl
  ~ xterm/vttests/dynamic.pl              ~ xterm/vttests/query-color.pl
  ~ xterm/vttests/resize.pl               ~ xterm/vttests/tcapquery.pl

  > Update to xterm 330 (matthieu@)

== xserver =========================================================== 03/03 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/xserver

xserver

  ~ hw/xfree86/drivers/modesetting/drmmode_display.c

  > Add code to update the value of the RandR "Backlight" property based on the
  > KMS connector property of the same name if such a property is present.
  > ok matthieu@ (kettenis@)

  ~ hw/xfree86/common/xf86pciBus.c        

  > Use the modesetting driver by default on 4th generation Intel Graphics and
  > later.  This matches what several Linux distros do these days as it tends
  > to
  > work better than the intel driver in most cases.
  > There are some performance issues with vncviewer on at least Ivy Bridge and
  > Haswell.  But for now that regression outweighs the benefits.
  > ok robert@, tedu@, sthen@ (kettenis@)

===============================================================================
_______________________________________________
owc mailing list
[email protected]
http://www.squish.net/mailman/listinfo/owc

Reply via email to