update doc and add release scripts

documentation/Doxyfile

@@ -31,7 +31,7 @@ PROJECT_NAME           = devLib2
 # This could be handy for archiving the generated documentation or 
 # if some version control system is used.
 
-PROJECT_NUMBER         = 2.5
+PROJECT_NUMBER         = 2.6
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
 # base path where the generated documentation will be put. 

documentation/mainpage.h

@@ -201,10 +201,10 @@ this is the only piece of information required to access the card.
 Below is an example implementation of myPCICardSetup().
 
 @code
-static const struct VMECSRID mydevids[] = {...}
+static const epicsPCIID mydevids[] = {...}
 
 int
-myVMECardSetup(const char* port,
+myPCICardSetup(const char* port,
                int b,
                int d,
                int f)

scripts/maketar.sh

@@ -0,0 +1,6 @@
+#!/bin/sh
+set -e
+
+TAG=$1
+
+exec git archive --prefix=devlib2-${1}/ --format tar.gz -9 -o devlib2-${1}.tar.gz ${1}

scripts/pushdoc.sh

@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+die() {
+    echo "$1"
+    exit 1
+}
+
+[ "$USER" ] || die "USER not set"
+
+[ -f documentation/mainpage.h ] || die "Run me in the top level"
+
+(cd documentation && doxygen)
+
+rsync -av --delete "$@" documentation/doc/html/ $USER,[email protected]:/home/project-web/epics/htdocs/devlib2/

scripts/uploadtar.sh

@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+die() {
+    echo "$1"
+    exit 1
+}
+
+[ -f "$1" ] || die "usage $0 <tarfile>"
+
+[ "$USER" ] || die "USER not set"
+
+[ -f documentation/mainpage.h ] || die "Run me in the top level"
+
+scp "$1" $USER,[email protected]:/home/frs/project/epics/devlib2/