Hi,

Eli asked that the source code and testcase files pertaining to python 
scripting support be renamed in order to support the 8.3 limitation in DOS. I
don't like the fnchange.lst solution because it's just one more arcane thing 
we would have to know in order to hack GDB. So I prefer straight renaming of 
the files.

How should said renaming be done, by submitting and committing a patch which 
removes the old file and adds a new one, or by moving things around in CVSROOT?

In any case, this is my suggestion for the source code files:

python/python-cmd.c -> python/py-cmd.c
python/python-frame.c -> python/py-frame.c
python/python-function.c -> python/py-function.c
python/python-prettyprint.c -> python/py-prettyprint.c
python/python-type.c -> python/py-type.c
python/python-utils.c -> python/py-utils.c
python/python-value.c -> python/py-value.c

and the testcase files:

gdb.python/python-cmd.exp -> gdb.python/py-cmd.exp
gdb.python/python-frame.c -> gdb.python/py-frame.c
gdb.python/python-frame.exp -> gdb.python/py-frame.exp
gdb.python/python-function.exp -> gdb.python/py-function.exp
gdb.python/python-mi.exp -> gdb.python/py-mi.exp
gdb.python/python-prettyprint.c -> gdb.python/py-prettyprint.c
gdb.python/python-prettyprint.exp -> gdb.python/py-prettyprint.exp
gdb.python/python-prettyprint.py -> gdb.python/py-prettyprint.py
gdb.python/python-template.cc -> gdb.python/py-template.cc
gdb.python/python-template.exp -> gdb.python/py-template.exp
gdb.python/python-value.c -> gdb.python/py-value.c
gdb.python/python-value.exp -> gdb.python/py-value.exp

I'll write changelogs before committing anything, of course.

I also have the two attached patches to adapt Makefile.in and the various test 
files (for the new test executable names).

Ok?
-- 
[]'s
Thiago Jung Bauermann