Index: trunk/Ohana/src/addstar/doc/ChangeLog.txt
===================================================================
--- trunk/Ohana/src/addstar/doc/ChangeLog.txt	(revision 5928)
+++ trunk/Ohana/src/addstar/doc/ChangeLog.txt	(revision 5928)
@@ -0,0 +1,47 @@
+
+
+- addstar 1.4
+  * major work to support SkyRegions
+  * cleaned up signed/unsigned inconsistencies
+  * fixed 2MASS time to use JD 
+
+2005.10.20 : addstar-1.3
+
+	This release incorportates many substantial improvements
+	needed to handle the panstarrs data problems:
+	- internal data representation now high precision
+	- multiple data storage formats (LONEOS, ELIXIR, PANSTARRS)
+	- multiple data storage modes (RAW, MEF, SPLIT)
+	- alternative matching scheme (-closest)
+	- sorted output tables now optional
+	- incremental updates possible for inserts
+	- client / server set now defined
+
+2005.08.15 : addstar-1.2
+
+        This is a snapshot release before I begin serious work on the
+	code to handle alternate formats and so forth needed for the
+	panstarrs support.  Minor updates since v1.1, mostly to fix
+	2MASS issues and to stay in sync with the libs.  
+
+2005.07.06 : addstar-1.1
+
+	I have made a variety of fairly substantial changes since
+        v1.0.  I have added autocode for the basic DVO data types.  I
+        have merged the functionality of addspphot, addrefs, and
+        addusno into the single addstar function.  There are now
+        options to add an ascii text table or stars from known
+        external reference catalogs (HST GSC, USNO, 2MASS).  Also, the
+        functions added for skyprobe (in-flight Mcal calculation,
+        color terms) are also incorporated.  I also substantially
+        re-organized the basic code to make the different modes more
+        sensible.  There are still a few changes needed for addstar
+        v2.0 (which will be able to handle the pan-starrs bandwidth).
+        specifically, addstar needs to handle the catalog files using
+        the TBD sky.db interfaces, it needs to interact with a DVO
+        server in a client/server way (to divide up the sky), it needs
+        to handle multiple versions of the table formats, and it might
+        need to know about the mysql backend interface.  
+
+2005.02.24 : I am adding the mosaic two-level astrometry information to the Image table.
+
Index: trunk/Ohana/src/addstar/doc/Changes.txt
===================================================================
--- trunk/Ohana/src/addstar/doc/Changes.txt	(revision 5903)
+++ 	(revision )
@@ -1,42 +1,0 @@
-
-
-2005.10.20 : addstar-1.3
-
-	This release incorportates many substantial improvements
-	needed to handle the panstarrs data problems:
-	- internal data representation now high precision
-	- multiple data storage formats (LONEOS, ELIXIR, PANSTARRS)
-	- multiple data storage modes (RAW, MEF, SPLIT)
-	- alternative matching scheme (-closest)
-	- sorted output tables now optional
-	- incremental updates possible for inserts
-	- client / server set now defined
-
-2005.08.15 : addstar-1.2
-
-        This is a snapshot release before I begin serious work on the
-	code to handle alternate formats and so forth needed for the
-	panstarrs support.  Minor updates since v1.1, mostly to fix
-	2MASS issues and to stay in sync with the libs.  
-
-2005.07.06 : addstar-1.1
-
-	I have made a variety of fairly substantial changes since
-        v1.0.  I have added autocode for the basic DVO data types.  I
-        have merged the functionality of addspphot, addrefs, and
-        addusno into the single addstar function.  There are now
-        options to add an ascii text table or stars from known
-        external reference catalogs (HST GSC, USNO, 2MASS).  Also, the
-        functions added for skyprobe (in-flight Mcal calculation,
-        color terms) are also incorporated.  I also substantially
-        re-organized the basic code to make the different modes more
-        sensible.  There are still a few changes needed for addstar
-        v2.0 (which will be able to handle the pan-starrs bandwidth).
-        specifically, addstar needs to handle the catalog files using
-        the TBD sky.db interfaces, it needs to interact with a DVO
-        server in a client/server way (to divide up the sky), it needs
-        to handle multiple versions of the table formats, and it might
-        need to know about the mysql backend interface.  
-
-2005.02.24 : I am adding the mosaic two-level astrometry information to the Image table.
-