[PATCH] xfree86: Remove unused message defines in Configint.h Signed-off-by: Jesse Adkins <jesserayadkins at gmail.com>

[Peter Hutterer]

On Sun, Aug 01, 2010 at 04:01:26PM -0700, Jesse Adkins wrote:
> ---
>  hw/xfree86/parser/Configint.h |    8 +-------
>  1 files changed, 1 insertions(+), 7 deletions(-)
> 
> diff --git a/hw/xfree86/parser/Configint.h b/hw/xfree86/parser/Configint.h
> index 05e40f6..f9d6166 100644
> --- a/hw/xfree86/parser/Configint.h
> +++ b/hw/xfree86/parser/Configint.h
> @@ -152,8 +152,6 @@ else\
>  "The %s keyword requires a boolean to follow it."
>  #define ZAXISMAPPING_MSG \
>  "The ZAxisMapping keyword requires 2 positive numbers or X or Y to follow it."
> -#define AUTOREPEAT_MSG \
> -"The AutoRepeat keyword requires 2 numbers (delay and rate) to follow it."
>  #define DACSPEED_MSG \
>  "The DacSpeed keyword must be followed by a list of up to %d numbers."
>  #define DISPLAYSIZE_MSG \
> @@ -185,8 +183,6 @@ else\
>  "Undefined Screen \"%s\" referenced by ServerLayout \"%s\"."
>  #define UNDEFINED_MODES_MSG \
>  "Undefined Modes Section \"%s\" referenced by Monitor \"%s\"."
> -#define UNDEFINED_DEVICE_MSG \
> -"Undefined Device \"%s\" referenced by Screen \"%s\"."
>  #define UNDEFINED_ADAPTOR_MSG \
>  "Undefined VideoAdaptor \"%s\" referenced by Screen \"%s\"."
>  #define ADAPTOR_REF_TWICE_MSG \
> @@ -211,10 +207,8 @@ else\
>  #define MUST_BE_OCTAL_MSG \
>  "The number \"%d\" given in this section must be in octal (0xxx) format."
>  
> -/* Warning messages */
> +/* Except this one, which is just a warning. */
>  #define OBSOLETE_MSG \
>  "Ignoring obsolete keyword \"%s\"."
> -#define MOVED_TO_FLAGS_MSG \
> -"Keyword \"%s\" is now an Option flag in the ServerFlags section."
>  
>  #endif /* _Configint_h_ */
> -- 
> 1.7.0.4

for commits like this it really helps if you can figure out when the
matching support was removed. the autorepeat one I remember, that's from the
keyboard driver cleanup which was first released with the latest or
second-to-latest keyboard driver release so that part should be ok.

git log -S<searchterm>
will give you which commits changed code with the given search term.

Cheers,
  Peter