It's completely unused; the obnoxious "DANGER!!!" comments
don't even explain what it was intended to do.
---
Do any code historians know what this was supposed to do?
Whatever the intent was, it hasn't been achieved for
quite a long time... unless that intent was "annoy"!

 src/openocd.c |   17 -----------------
 1 file changed, 17 deletions(-)

--- a/src/openocd.c
+++ b/src/openocd.c
@@ -51,21 +51,6 @@
 #define OPENOCD_VERSION \
                "Open On-Chip Debugger " VERSION RELSTR " (" PKGBLDDATE ")"
 
-static void print_version(void)
-{
-       /* DANGER!!! make sure that the line below does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line below does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line below does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line below does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line below does not appear in a patch, 
do not remove */
-       LOG_OUTPUT("$URL$\n");
-       /* DANGER!!! make sure that the line above does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line above does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line above does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line above does not appear in a patch, 
do not remove */
-       /* DANGER!!! make sure that the line above does not appear in a patch, 
do not remove */
-}
-
 /* Give TELNET a way to find out what version this is */
 COMMAND_HANDLER(handle_version_command)
 {
@@ -257,8 +242,6 @@ int openocd_main(int argc, char *argv[])
        }
 #endif
 
-       print_version();
-
        LOG_OUTPUT("For bug reports, read\n\t"
                "http://openocd.berlios.de/doc/doxygen/bugs.html";
                "\n");
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to