[cmor] 60/190: 2010-09-29 : Cleaned up error messages, now tries to output var/axis it was working on as well as table used. 2010-09-29 : When value that exceeds valid_min/max is found, now returns location of extreme point instead of first point encountered, as well as actuall coordinates values (not just indices) 2010-09-22 : Joerg found a bug that was due to checking only the refvar.dimension w/o checking the actual tables as well 2010-09-01 : fixed a bug on mac 32bit when reading in net3 version string 2010-09-01 : some vars with grid and singleton dims were wrongly analyzed by cmor_variable has not being defined with the right number of dimmensions. 2010-09-01 : updated doc. Was saying you can pass "none" for units when it really is: "" 2010-09-01 : updated doc. Was wrongly stating you can pass "none" if no missing_value 2010-08-24 : when writing time only variables, the time_bnds would fail to write if passed at cmor_write time.

Alastair McKinstry mckinstry at moszumanska.debian.org
Tue Jul 21 12:54:37 UTC 2015


This is an automated email from the git hooks/post-receive script.

mckinstry pushed a commit to branch debian/master
in repository cmor.

commit 1b68bd52a44c1ff1a22ed34b2f4e579c217abe2c
Author: Charles Doutriaux <doutriaux1 at llnl.gov>
Date:   Wed Oct 6 08:44:21 2010 -0700

    2010-09-29 : Cleaned up error messages, now tries to output var/axis it was working on as well as table used.
    2010-09-29 : When value that exceeds valid_min/max is found, now returns location of extreme point instead of first point encountered, as well as actuall coordinates values (not just indices)
    2010-09-22 : Joerg found a bug that was due to checking only the refvar.dimension w/o checking the actual tables as well
    2010-09-01 : fixed a bug on mac 32bit when reading in net3 version string
    2010-09-01 : some vars with grid and singleton dims were wrongly analyzed by cmor_variable has not being defined with the right number of dimmensions.
    2010-09-01 : updated doc. Was saying you can pass "none" for units when it really is: ""
    2010-09-01 : updated doc. Was wrongly stating you can pass "none" if no missing_value
    2010-08-24 : when writing time only variables, the time_bnds would fail to write if passed at cmor_write time.
---
 RELEASE-NOTES  | 1 +
 configure.ac   | 2 +-
 include/cmor.h | 4 ++--
 3 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index ddd772d..7f66044 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -1,3 +1,4 @@
+2010-10-06 : tagging 2.3
 2010-09-29 : Cleaned up error messages, now tries to output var/axis it was working on as well as table used.
 2010-09-29 : When value that exceeds valid_min/max is found, now returns location of extreme point instead of first point encountered, as well as actuall coordinates values (not just indices)
 2010-09-22 : Joerg found a bug that was due to checking only the refvar.dimension w/o checking the actual tables as well
diff --git a/configure.ac b/configure.ac
index b1bfccb..81346b0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2,7 +2,7 @@ dnl                                                -*- Autoconf -*-
 dnl  Process this file with autoconf to produce a configure script.
 
 dnl AC_PREREQ(2.59)
-AC_INIT(cmor, 2.2.1, doutriaux1 at llnl.gov)
+AC_INIT(cmor, 2.3.0, doutriaux1 at llnl.gov)
 
 GIT_TAG=`./get_git_version.sh`
 
diff --git a/include/cmor.h b/include/cmor.h
index c15522f..10c50a0 100644
--- a/include/cmor.h
+++ b/include/cmor.h
@@ -19,8 +19,8 @@
 #define CMOR_EXIT_ON_WARNING 2
 
 #define CMOR_VERSION_MAJOR 2
-#define CMOR_VERSION_MINOR 2
-#define CMOR_VERSION_PATCH 1
+#define CMOR_VERSION_MINOR 3
+#define CMOR_VERSION_PATCH 0
 #define CMOR_CF_VERSION_MAJOR 1
 #define CMOR_CF_VERSION_MINOR 4
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-science/packages/cmor.git



More information about the debian-science-commits mailing list