commit 6f714830da6c8d74f024be6b0bb32c1ea39c1217
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sat Dec 3 15:47:06 2022 -0800

    xrandr 1.5.2
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 213e10f1996b08305df55c237c90152227e0c5f7
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Fri Oct 28 18:29:04 2022 -0700

    Constify array argument to find_last_non_clamped()
    
    Suggested by cppcheck:
    
    xrandr.c:1046:30: style: Parameter 'array' can be declared with const [constParameter]
    find_last_non_clamped(CARD16 array[], int size)
                                 ^
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit fc331d39447412320e856f56bab88613264cd8f5
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Fri Oct 28 18:25:19 2022 -0700

    Remove unused definition of rectangle_t
    
    Was added in commit 854a7c2916455fec5e but never used.
    Reported by cppcheck unusedStructMember warning.
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit e8c4a2727196c8f9bf76df30c5c0a8671e0e5dfe
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Fri Oct 28 18:22:11 2022 -0700

    Remove unused macros left over from original RandR 1.2 code
    
    Use of these was removed in commit cb017692883daf64 in 2006.
    Reported by clang -Wunused-macros
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 3613fea4472741d8423c38a82e5569739d53bbb7
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Fri Oct 28 18:09:58 2022 -0700

    Fix a -Wsign-compare warning
    
    xrandr.c: In function ‘main’:
    xrandr.c:2780:24: warning: comparison between signed and unsigned integer
      expressions [-Wsign-compare]
          for (int t = 0; t < sizeof(filter_names) / sizeof(filter_names[0]); t++)
                            ^
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 289722fc8f2c9916a9631c7e4c796269b99b98f8
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Fri Oct 28 18:07:20 2022 -0700

    Variable scope reductions as suggested by cppcheck
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 8231beec67ee274d10b5d4c5b910d673dc6d1cc8
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Thu Jul 28 17:30:21 2022 -0700

    gitlab CI: stop requiring Signed-off-by in commits
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 2fb90d4d626dcc0432f96da3fa438724d637bdd3
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sun Jan 9 12:38:26 2022 -0800

    Fix spelling/wording issues
    
    Found by using:
        codespell --builtin clear,rare,usage,informal,code,names
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 296effc3ac7b2f095e889488d82e9d1a4fffd824
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Tue Dec 7 13:34:30 2021 -0800

    gitlab CI: add a basic build test
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 824484e5ba50f1e6858ea990393c181a249c3a5e
Author: Matt Turner <mattst88@gmail.com>
Date:   Mon Aug 12 10:42:41 2019 -0700

    xrandr 1.5.1
    
    Signed-off-by: Matt Turner <mattst88@gmail.com>

commit edac280f06da2ad2256c710f95b34253202e6e49
Author: Matt Turner <mattst88@gmail.com>
Date:   Mon Aug 12 10:49:52 2019 -0700

    Build xz tarballs instead of bzip2
    
    Signed-off-by: Matt Turner <mattst88@gmail.com>

commit 829ed54d89bb37c9e2f8050fe72bd4ecf7b5395a
Author: Vladimir Panteleev <git@thecybershadow.net>
Date:   Thu Dec 20 11:28:51 2018 +0000

    xrandr: Fix deleting inactive monitors
    
    The following commands did not behave correctly:
    
    xrandr --setmonitor empty auto none
    xrandr --delmonitor empty
    
    The second command failed with "No monitor named 'empty'". This
    occurred because get_monitors was invoked with its get_active argument
    set to False, which caused it to not retrieve inactive monitors. Thus,
    inactive monitors could not be deleted.
    
    Fix this bug by invoking get_monitors (and, thus, XRRGetMonitors) with
    get_active = False, thus enabling deletion of disabled monitors.
    
    Signed-off-by: Matt Turner <mattst88@gmail.com>

commit 9e5fa7c8c26f78e121ffad0d7a745a674c4a1849
Author: Adam Simpkins <adam@adamsimpkins.net>
Date:   Thu Aug 3 15:11:53 2017 -0700

    xrandr: fix crash if some modes cannot be found
    
    When printing modes in "xrandr -q", check to see if we failed to look up
    mode information from a mode XID.  Previously the command would
    dereference null and crash if the mode information could not be found.
    
    When using an external HDMI monitor on a laptop with a Skylake Intel
    graphics chipset "xrandr -q" occasionally is unable to look up mode
    information for some of the modes.  It seems likely there is some other
    sort of library or driver issue causing these lookup failures, but this
    change to xrandr at least prevents it from segfaulting.
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 3316ccaca35dc5fc6b6e3b5826e222cd648eb9c9
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Wed Nov 21 17:17:09 2018 -0800

    Update configure.ac bug URL for gitlab migration
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 004681fb9c71256feb49e2bda203819654b0a05f
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Fri Nov 16 22:47:41 2018 -0800

    Update README for gitlab migration
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit a2134406ab0aef44e7b710e1e2a2a40965e96692
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Thu Sep 13 09:44:16 2018 +1000

    init the name to 0
    
    There are a few conditions where coverity finds a use of an uninitialized
    field of the name_t struct. These are rather messy combinations of conditions,
    so let's go with the simple solution here and just init everything to 0.
    This may still have side-effects but at least they'll be more obvious than the
    previous "use whatever memory is leftover from breakfast".
    
    This patch also adds a missing init_name(), much for the same reason.
    
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

commit 9882680c9f7f433a47514a9cb799c79e3e10a024
Author: Pali Rohár  <pali.rohar@gmail.com>
Date:   Sat Mar 10 16:23:29 2018 +0100

    Document that --dpi and --fbmm options set DPI of whole X screen
    
    Explicitly document and make it clear that those options do not change
    DPI of some monitor output. Also state that these options have no useful
    meaning for multi-monitor configuration.
    
    Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
    Reviewed-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>

commit da61a8bd95bd20d45397eee6a6c0d3ad5a50c399
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Tue Feb 6 22:02:42 2018 +0100

    xrandr: gamma and scaling factors must be positive
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Keith Packard <keithp@keithp.com>

commit 5e95248b5bab1254ecedffb6cb681b0ee06c0f29
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Mon Feb 5 02:01:21 2018 +0100

    xrandr.man: document the monitor manipulation options
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Keith Packard <keithp@keithp.com>

commit cf25d585df5582d29528acc35f1c91dcb98b0f00
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Mon Feb 5 01:31:15 2018 +0100

    xrandr: allow single value for --gamma
    
    Similarly to --scale, accept a single value to be used for all three
    components, and refuse values with extra junk after the acceptable
    values.
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Keith Packard <keithp@keithp.com>

commit 289bc0f1c53d8bc488d96e7f79afabd361758e08
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Sun Jul 16 14:57:40 2017 +0200

    xrandr.man: grammar tuning
    
    Rephrase the --scale option paragraph to improve English and be more
    consistent in choice of plurals and tense. Also ensure that each
    sentence starts on a new line in the roff source.
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Keith Packard <keithp@keithp.com>

commit 635a4c8bc9f81852dc77b5dc9de1ce5825849a7f
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Sun Jul 16 15:05:21 2017 +0200

    xrandr: stricter --scale argument parsing
    
    We used to accept something like --scale 2x3junk as a valid input
    (scaling x by 2 and y by 3), even though this isn't really a valid
    scaling factor.
    
    Fix by making sure there is nothing after the parsed number(s).
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Keith Packard <keithp@keithp.com>

commit 4e655b2cfc79b02d0ca7cea82b09f1f1133f1a0a
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Wed May 17 17:20:50 2017 +0200

    xrandr: allow a single value for --scale
    
    This allows using e.g. --scale 0.5 as a shorthand for --scale 0.5x0.5
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Keith Packard <keithp@keithp.com>

commit 8969b3c651eaae3e3a2370ec45f4eeae9750111d
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Thu Jun 1 15:45:59 2017 -0700

    man: Document the new --filter option
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

commit 6ac2afc0d7d8d51d4085767b901667393c11061b
Author: Pablo De La Garza <pdelagarza@nvidia.com>
Date:   Thu Mar 23 16:05:02 2017 -0700

    xrandr: Add a "--filter" flag
    
    Flag can be set to "nearest" or "bilinear"
    
    Signed-off-by: Pablo De La Garza <pdelagarza@nvidia.com>
    [aplattner@nvidia.com: Fixed style and whitespace]
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 5d5db88d106a49d7560a8042fa054df8b609f00a
Author: Pali Rohár  <pali.rohar@gmail.com>
Date:   Sun May 28 23:33:26 2017 +0200

    Document format of --dpi option in non-ambiguous way
    
    Slash in previous documentation could be misunderstood as part of the
    --dpi command line option. So fix it.
    
    Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

commit 215a01f1513f918e7295a8a477d4674f7b8085f0
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Wed Jan 18 08:52:23 2017 +0100

    xrandr: suppress misleading indentation warning
    
    When printing out rotations, we print a space before any item other than
    the first, and set `first = False` in each block where we print.
    However, this is done in the same line as the conditional that checks if
    first is set, which may give the impression that the assignment is also
    under the conditional. This is not the case, and recent GCC warns about
    this.
    
    Move the assignment to after we print the value we want to print, which
    (1) doesn't mislead about the indentation, and
    (2) makes logical sense as the _next_ entry is what won't be the first.
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>

commit 85e95db7120da3bdaf9efb3033be5f9338e6c328
Author: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date:   Wed Jan 18 08:52:09 2017 +0100

    xrandr: document that we accept '--dpi output'
    
    Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>

commit 1b561d25d197069a4a2c8b5d4007938b669ee612
Author: Mihail Konev <k.mvc@ya.ru>
Date:   Thu Jan 26 14:00:21 2017 +1000

    autogen: add default patch prefix
    
    Signed-off-by: Mihail Konev <k.mvc@ya.ru>

commit f84206b8cdbb9c6211c845da92492346bae8fde0
Author: Emil Velikov <emil.l.velikov@gmail.com>
Date:   Mon Mar 9 12:00:52 2015 +0000

    autogen.sh: use quoted string variables
    
    Place quotes around the $srcdir, $ORIGDIR and $0 variables to prevent
    fall-outs, when they contain space.
    
    Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
    Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

commit bd3f2f58351a038469c7adc6be7650087433f6f4
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Tue Jan 24 10:32:07 2017 +1000

    autogen.sh: use exec instead of waiting for configure to finish
    
    Syncs the invocation of configure with the one from the server.
    
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
    Reviewed-by: Emil Velikov <emil.velikov@collabora.com>

commit 65fd628cdfd1c95bd01a50706d4577655d1dd404
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Tue Feb 23 10:22:26 2016 -0800

    xrandr 1.5.0
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit d62030b506f6b686ffe1e750ea9d3a855beec1f0
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Sun Sep 13 11:40:37 2015 +0100

    Only use the current information when setting modes
    
    Before we change the state (e.g. adding a mode or applying one to an
    output), we query the screen resources for the right identifiers. This
    should only use the current information rather than force a reprobe on
    all hardware - not only can that reprobe be very slow (e.g. EDID
    timeouts on the order of seconds), but it may perturb the setup that the
    user is trying to configure.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

commit 3d03be780fca4949b11ead46c5ea5d3266c03c32
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jun 18 08:27:49 2015 +0100

    Mark all CRTC as currently unused for second picking CRTC pass
    
    We perform two passes over the CRTC in order to find the preferred CRTC
    for each enabled output. In the first pass, we try to preserve the
    existing output <-> CRTC relationships (to avoid unnecessary flicker).
    If that pass fails, we try again but with all outputs first disabled.
    However, the logic to preserve an active CRTC was not disabled along
    with the outputs - meaning that if one was active but its associated
    output was disabled by the user, then that CRTC would remain unavailable
    for other outputs. The result would be that we would try to assign more
    CRTC than available (i.e. if the user request 3 new HDMI outputs on a
    system with only 3 CRTC, and wished to switch off an active internal
    panel, we would report "cannot find CRTC" even though that configuration
    could be established.)
    
    Reported-and-tested-by: Nathan Schulte <nmschulte@gmail.com>
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

commit 53ef3fc13b3e282902892e3140765460c6f93276
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jun 18 08:27:48 2015 +0100

    Mark disabling an output as a change in its CRTC
    
    When an output is disabled via the cmdline, we can use that information
    to prevent assigning the current CRTC to the output and free it up for
    reuse by other outputs in the first pass of picking CRTC.
    
    Reported-and-tested-by: Nathan Schulte <nmschulte@gmail.com>
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

commit 09989b09a342b273ee30e1d96267dced3cbe61b0
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Thu Apr 9 11:14:54 2015 -0700

    Split verbose mode printing into a helper function
    
    Combine the two forms of verbose mode printing into a single function.  Pass the
    'current' and 'preferred' flags as arguments.  This fixes the code that prints
    unassociated modes to print the flags as well.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>

commit d06730e94320175d40ff6f2bb38dce55312f2e54
Author: Keith Packard <keithp@keithp.com>
Date:   Tue Dec 16 01:57:45 2014 -0800

    Add monitor support (v2)
    
    This adds the ability to query, set and delete monitors
    
    v2: [airlied] add list active monitors
    
    Reviewed-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Keith Packard <keithp@keithp.com>

commit 3076c3494b6f3f00b9c4509c2dab6f40858af4cf
Author: Dave Airlie <airlied@redhat.com>
Date:   Tue Mar 31 11:49:00 2015 +1000

    xrandr: don't return NULL from a void
    
    Reported-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>

commit 6957ad0cf3cdd10e8f4a5638b36f25c7a9b4ea25
Author: Dave Airlie <airlied@redhat.com>
Date:   Mon Mar 30 14:51:49 2015 +1000

    xrandr: parse property returns correctly.
    
    Xlib uses longs for 32-bit, so when we get values back they
    are in longs, this fixes the xrandr parsing code to parse
    the correct sized values according to Xlib.
    
    Reviewed-by: Keith Packard <keithp@keithp.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>

commit f429a517684e8f99c15bc2858e62bbd112331456
Author: Keith Packard <keithp@keithp.com>
Date:   Wed Oct 8 13:16:07 2014 +0200

    keystone: Report matrix error. Deal with "primary" in xrandr output
    
    Compute the error cause by the fixed point matrix representation and
    display that.
    
    Accept the 'primary' word found in xrandr output and ignore it.
    
    Signed-off-by: Keith Packard <keithp@keithp.com>

commit 527d83dde0cb78cbfbb67d203d073e41e110d4a1
Author: Keith Packard <keithp@keithp.com>
Date:   Mon Jul 9 10:52:52 2012 -0700

    Increase keystone.5c default window size

commit 9887ed4989e0abd48004598be0eb5cb06fa40bd1
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Aug 1 23:14:42 2014 -0700

    xrandr 1.4.3
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 20d76f773cf8de474cf7a3f1082961605732c3f1
Merge: 00477d8 193a358
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Aug 1 23:10:46 2014 -0700

    Merge commit '193a358'
    
    Conflicts:
            xrandr.c

commit 193a358563a59c1a3fc55f55029c605e2419c80b
Author: Stéphane Aulery  <lkppo@free.fr>
Date:   Sat Jun 29 16:50:25 2013 -0700

    Mention of --brightness with -h option
    
    Reported by jidanni at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709569
    
    Signed-off-by: Stéphane Aulery <lkppo@free.fr>
    Reviewed-By: Matt Dew <marcoz@osource.org>
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 00477d88297eaa6c87aa144548590c32540e3928
Author: Connor Behan <connor.behan@gmail.com>
Date:   Tue Jun 10 23:56:12 2014 -0700

    Allow -x and -y switches to undo themselves
    
    People who want to dick around might think it is safe to run "xrandr -x"
    before they know any of the other syntax. When "xrandr -x" again does
    not get back to a normal screen, they are stuck having to read a manpage
    with reflected text.
    
    Signed-off-by: Connor Behan <connor.behan@gmail.com>
    Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
    Tested-by: Aaron Plattner <aplattner@nvidia.com>
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 7d464312fb84c080a6e287edd21a794193a0dd78
Author: Connor Behan <connor.behan@gmail.com>
Date:   Sun Jun 1 16:35:50 2014 -0700

    Remove duplicate printing of the axis
    
    Even in verbose mode, why print the same information twice?
    
    Signed-off-by: Connor Behan <connor.behan@gmail.com>
    Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 792f05ea20d5191425154470760e36dcf023c6e9
Author: Dominik Behr <dbehr@chromium.org>
Date:   Tue Apr 1 18:38:05 2014 -0700

    xrandr: use full range for gamma table generation
    
    Calculate gamma table using full [0,65536) range and do not make any
    assumptions about relation of gamma table size and significant bits.
    
    Gamma table size has nothing to do with number of significant bits in hardware.
    In particular we are dealing now with gamma table that has 17 entries and 8
    bit precision, there are other GPUs with 10 bit precision and less than 256
    entries using partial linear approximation. Deriving assumed gamma table
    significant bits from size of gamma table leads to incorrect calculations and
    loss of precision. Also XRandR specification never mentions that gamma tables
    need to be power of 2.
    
    Signed-off-by: Dominik Behr <dbehr@chromium.org>
    Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

commit 866366d0825c3f488abd58960e4f76ae50de08d1
Author: Thomas Klausner <wiz@NetBSD.org>
Date:   Sat Mar 29 00:50:17 2014 +0100

    Remove unnecessary parentheses.
    
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Thomas Klausner <wiz@NetBSD.org>

commit 31f5fa6a47db154abb47cf16e9f6cc4d983ad371
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Thu Mar 27 11:37:07 2014 -0700

    xrandr 1.4.2
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 934a424a05a296c0b8af015476e11b191d55eba3
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Mar 21 10:35:56 2014 -0700

    xrandr: document how to disconnect RandR 1.4 providers
    
    Commit a6217be2d5a93a4c7b48f4081a4a8e14c3c97014 restored the ability to
    disconnect RandR 1.4 providers from each other, but it's not clear from the
    documentation how to actually do that.  Try to clarify by mentioning it in the
    man page.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Dave Airlie <airlied@redhat.com>

commit a6217be2d5a93a4c7b48f4081a4a8e14c3c97014
Author: Dave Airlie <airlied@gmail.com>
Date:   Fri May 3 10:05:04 2013 +1000

    xrandr: allow disconnecting of offload and outputs
    
    Before the lookup code passing a 0 XID would disconnect,
    this fixes it backup.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
    Tested-by: Aaron Plattner <aplattner@nvidia.com>
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 00c795e99fe29ecd56e05e915e508c7af0ac39ad
Author: Ville Syrjälä < <ville.syrjala@linux.intel.com>
Date:   Fri May 31 17:01:54 2013 +0300

    xrandr: Use floating point for VTotal when calculating refresh rate
    
    Interlaced modes generally have an odd VTotal, so we lose half a line
    from VTotal when we divide by two. That causes the final refresh rate
    to be slightly off. Make VTotal a double to avoid the problem.
    
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Reviewed-by: Aaron Plattner <aplattner@nvidia.com>

commit 8f9b993342fddfceaa1afbec2996ce10038f10d7
Author: Ville Syrjälä < <ville.syrjala@linux.intel.com>
Date:   Fri May 31 17:01:53 2013 +0300

    xrandr: Use more decimal places when printing various rates
    
    Using just one decimal place for dotclock and refresh rates loses quite
    a bit of information. When dealing with 60Hz vs. 59.94Hz refresh rate
    modes for example, it's useful to see at least two decimal places. For
    the dotclock in similar cases, three decimal places seems quite a bit
    better than just one.
    
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Reviewed-by: Aaron Plattner <aplattner@nvidia.com>

commit 7ede207f9064fd88427026e38818819c2c8422bb
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Jan 3 05:48:17 2014 -0800

    Special-case printing of the GUID property
    
    Rather than printing GUIDs as 16 signed decimal integers, print them in
    {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} format.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>

commit e7a19c8b5a26c8bfd76a7399a1a15eac01184261
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Jan 3 05:22:02 2014 -0800

    Move EDID printing into a helper function
    
    Localize the specialness of EDID printing by moving it into a single function,
    print_edid, which prints the binary EDID data.  Remove the is_edid parameter
    from everything else.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>

commit a29728ca9599fd08da1243e9b422ac26a24cc05b
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Jan 3 05:14:35 2014 -0800

    Split output property printing into a helper function
    
    Move the body of the code that prints the actual output property values into a
    helper function.  This will make it easier for this function to select
    special-case property printers for properties that need special formatting.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>

commit c5334bb4137d6ea7b8c8b10d51131b9450d1106b
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Tue Jul 16 23:30:27 2013 -0700

    xrandr 1.4.1

commit 0e0b47341a45c138082d9f8047dcbdb91b90155d
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sat Jul 13 00:11:41 2013 -0700

    Combine usage message strings
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 38772ec3b5a7216a88676f95b5edc764dd0a23d6
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sat Jul 13 00:07:26 2013 -0700

    Declare capability_name() as returning const char *
    
    Only used as an argument to printf.   Clears gcc warnings:
    xrandr.c: In function ‘capability_name’:
    xrandr.c:237:2: warning: return discards ‘const’ qualifier from pointer target type [enabled by default]
    xrandr.c:239:2: warning: return discards ‘const’ qualifier from pointer target type [enabled by default]
    xrandr.c:241:2: warning: return discards ‘const’ qualifier from pointer target type [enabled by default]
    xrandr.c:243:2: warning: return discards ‘const’ qualifier from pointer target type [enabled by default]
    xrandr.c:245:5: warning: return discards ‘const’ qualifier from pointer target type [enabled by default]
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit f53d8511d26a26e9bd6b1bc665f6283f1efd98d9
Author: Thomas <fischer@unix-ag.uni-kl.de>
Date:   Fri Nov 9 14:33:08 2012 +0000

    Bug 56923 - Make command line options consistent (single vs double dash)
    
    Most of xrandr's command line options follow the system of single
    dashes for single character options (e.g. "-v") and double dashes for
    long options ("--version").  The only exceptions are "-display" and
    "-help", most likely for historical reasons.  To make the behavior
    consistent across all options, the following patch adds "--display"
    and "--help" as alternatives to the current inconsistency.  The man
    page got updated as well, recommending double-dash variants for both
    options. The old behavior is still supported, so the patch should not
    break any existing usage/script.
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit bd1502f50f0c230798bdce99dec6efc76791c024
Author: Thomas Klausner <wiz@NetBSD.org>
Date:   Sun Jun 2 21:30:39 2013 +0200

    Protect config.h like usual.
    
    Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com>
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit ace5e2b21b2a204f94c6452fa0d8f36699aec249
Author: Andy Ritger <aritger@nvidia.com>
Date:   Thu May 2 01:20:27 2013 -0700

    xrandr: calloc XRRModeInfo's passed to libXrandr.
    
    The "--newmode" commandline option initializes an XRRModeInfo and passes
    it into XRRCreateMode().  calloc(3) it to avoid uninitialized fields.
    For consistency, calloc(3) all the places where umode_t's (the wrapper
    structure for XRRModeInfo) are allocated.
    
    Signed-off-by: Andy Ritger <aritger@nvidia.com>
    Tested-by: Nikhil Mahale <nmahale@nvidia.com>
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit eb17ad8adc9400f6ed252872f13ccf5551f9e2e9
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Thu Feb 28 12:01:53 2013 -0800

    Print spaces between XA_ATOM property values
    
    Commit b26fd532b3dab222956ea27eef4e41345978b5b2 redid how xrandr prints
    properties.  It neglected to put spaces between the values of XA_ATOM
    properties, so they all run together.  For example,
    
        audio: auto
            supported: force-dvioffautoon
    
    Fix this by putting a space after each atom name.  In addition, some drivers
    create property values with spaces in them, so put commas between entries to
    disambiguate.  For example,
    
        Broadcast RGB: Automatic
            supported: Automatic, Full, Limited 16:235
    
    Do the same for properties with multiple valid ranges.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>

commit 222f245fb3a00308cb3ff491f5c84ac9c69c3253
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Tue Feb 12 13:24:38 2013 -0800

    xrandr 1.4.0
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>

commit 3e5f160c4198a5160be5e9a3f21ba3f4130d4318
Merge: dac72db bd16618
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Tue Feb 12 12:30:20 2013 -0800

    Merge branch 'fixes'
    
    Conflicts:
            xrandr.c

commit bd166184f6c1973ae2f5f99d040733db3e9e82cf
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Wed Feb 6 14:21:57 2013 -0800

    Cast XID to unsigned int to suppress a printf warning
    
    Sorry I forgot about this in commit 138b6252c0cae6599b6c8a25ffa22ffe70f227c2.
    That change introduced a warning:
    
      xrandr.c|645 col 5| warning: format ‘%x’ expects argument of type ‘unsigned int’, but argument 2 has type ‘XID’ [-Wformat]
    
    Fix that by just casting the XID to unsigned int.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Daniel Dadap <ddadap@nvidia.com>

commit 7fd4f18b649f22fad4dbf9fc64b69b3e7f172207
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Wed Feb 6 11:13:06 2013 -0800

    Bug #37043: adjust refresh rates for doublescan and interlace
    
    These two flags halve and double, respectively, the effective refresh rate of a
    mode.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Daniel Dadap <ddadap@nvidia.com>

commit d752d524027fbc20d9fdee06fed173e454f15370
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Wed Feb 6 10:10:03 2013 -0800

    Bug #29603: document that there might be multiple preferred modes
    
    The X server sorts the mode list for an output with preferred modes first, and
    specifies how many preferred modes there are by setting the npreferred field in
    the XRRModeInfo structure.
    
    Update the man page to refer to preferred modes in the plural, and mention that
    --auto and --preferred use the *first* preferred mode.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Daniel Dadap <ddadap@nvidia.com>

commit b2f0bd198b1116e45389a6628b657b722b4102a4
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Wed Feb 6 14:11:23 2013 -0800

    Bug #14118: print usage() to stdout, proper errors for bad arguments
    
    Print the usage() text to stdout instead of stderr, and then only if -help is
    specified.  Also allow --help for consistency.
    
    For other command line syntax errors, introduce a new helper function argerr()
    that prints errors of the form
    
      xrandr: %s
      Try './xrandr --help' for more information.
    
    and exits.  Use that to print proper error messages.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Daniel Dadap <ddadap@nvidia.com>

commit 0a26e076e10a3c7461d59c830cdc10688d66824f
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Wed Feb 6 13:08:58 2013 -0800

    Bug #11397: check that numeric --orientation arguments are in range
    
    The only valid parameters to -o (--orientation) are 0, 1, 2, 3, normal, left,
    inverted, and right.  xrandr converts the strings to numbers and then checks
    that they're within range, but doesn't validate them if it was numeric to begin
    with.
    
    Move the range check outside of the if statement so that out-of-range numeric
    values are rejected properly.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Daniel Dadap <ddadap@nvidia.com>

commit dac72dbbc7501483eccec71bbf0db05a56756109
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Fri Aug 24 21:43:13 2012 -0700

    xrandr: Fix variable declaration warnings
    
    There are piles of places in the code where a variable shadows either another
    variable or a global function:
    
      xrandr.c:545:35: warning: declaration of ‘index’ shadows a global declaration [-Wshadow]
      xrandr.c:574:9: warning: declaration of ‘index’ shadows a global declaration [-Wshadow]
      xrandr.c:967:19: warning: declaration of ‘gamma’ shadows a global declaration [-Wshadow]
      xrandr.c:1329:16: warning: declaration of ‘gamma’ shadows a global declaration [-Wshadow]
      xrandr.c:2055:28: warning: declaration of ‘outputs’ shadows a global declaration [-Wshadow]
      xrandr.c:2068:29: warning: declaration of ‘outputs’ shadows a global declaration [-Wshadow]
      xrandr.c:2928:16: warning: declaration of ‘output’ shadows a previous local [-Wshadow]
      xrandr.c:2995:15: warning: declaration of ‘output’ shadows a previous local [-Wshadow]
      xrandr.c:3016:15: warning: declaration of ‘j’ shadows a previous local [-Wshadow]
      xrandr.c:3018:19: warning: declaration of ‘rotations’ shadows a previous local [-Wshadow]
      xrandr.c:3116:15: warning: declaration of ‘crtc’ shadows a previous local [-Wshadow]
      xrandr.c:3170:8: warning: declaration of ‘k’ shadows a previous local [-Wshadow]
      xrandr.c:3243:20: warning: declaration of ‘mode’ shadows a previous local [-Wshadow]
    
    'index' and 'gamma' are C library functions:
    
      index (3)            - locate character in string
      gamma (3)            - (logarithm of the) gamma function
    
    The rest of these are either variables or function parameters.
    
    When possible, move the declaration of a variable into the block where it is
    used, including in cases where the same variable is used in multiple blocks but
    the later block doesn't depend on the value from the earlier block.
    
    In a few cases, rename the variable in the outer scope to be more specific (e.g.
    output -> config_output) so the more generic variable in the inner scope (e.g.
    the 'output' variable used to iterate over all outputs) doesn't have to change.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Andy Ritger <aritger@nvidia.com>

commit 138b6252c0cae6599b6c8a25ffa22ffe70f227c2
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Mon Feb 4 16:17:24 2013 -0800

    xrandr: look for providers by name or xid
    
    Use the name_t infrastructure to allow specifying providers by name, index, or
    XID.  This means that numbers without a "0x" prefix will now be interpreted as a
    indices rather than XIDs.  To match that, print provider XIDs in hexadecimal.
    
    Print an error if a provider-related option is specified and RandR 1.4 isn't
    supported.
    
    Make get_screen robust against being called multiple times.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Dave Airlie <airlied@redhat.com>

commit a93b77b15fa2463c7fd06c6898b9c9f737c3ae8a
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Mon Feb 4 16:05:11 2013 -0800

    xrandr: make providers a first-class citizen
    
    Create a struct _provider to match the existing output, crtc, etc. objects.
    Build that from a new get_providers() function.  Use that to populate the list
    when querying the providers.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Dave Airlie <airlied@redhat.com>

commit 8ce9d1fa48a7556e9aee090e5d72566dbb9a32f8
Author: Aaron Plattner <aplattner@nvidia.com>
Date:   Mon Feb 4 15:20:21 2013 -0800

    man: document provider options
    
    I hope I got the --setprovideroffloadsink parameters the right way around.
    
    Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
    Reviewed-by: Dave Airlie <airlied@redhat.com>

commit d07ef58f0cb6920dedc00c1e39cc6a5d0f31775e
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sun Jan 20 12:32:15 2013 -0800

    Fix -Wformat warnings about passing longs where ints were expected
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit ee548dde0f5bcc6503ad2f74af5261fbf022dada
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sun Jan 20 12:28:04 2013 -0800

    Mark fatal() and warning() as taking printf-style arguments
    
    Silences -Wformat-nonliteral warnings about them passing through
    unknown format arguments to vfprintf.
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit 77b03188b14cdef4523184a73b25fb2703d52685
Author: Alan Coopersmith <alan.coopersmith@oracle.com>
Date:   Sun Jan 20 12:24:24 2013 -0800

    config: Add missing AC_CONFIG_SRCDIR
    
    Regroup AC statements under the Autoconf initialization section.
    Regroup AM statements under the Automake initialization section.
    
    Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

commit a9a92e85b2f8ea54855a3b45eb0882d7da50c1a8
Author: Colin Walters <walters@verbum.org>
Date:   Wed Jan 16 13:02:57 2013 -0500

    autogen.sh: Honor NOCONFIGURE=1
    
    See http://people.gnome.org/~walters/docs/build-api.txt
    
    Signed-off-by: Adam Jackson <ajax@redhat.com>

commit 4a15ed3b1edd22d67307620f2265faf365700519
Author: Adam Jackson <ajax@redhat.com>
Date:   Wed Jan 16 13:03:39 2013 -0500

    configure: Drop AM_MAINTAINER_MODE
