[Darshan-commits] [Darshan] branch, dev-modular, updated. aa56e9028038ce4c0c807bee4b0bcdd1797bb496

[Service Account]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "".

The branch, dev-modular has been updated
       via  aa56e9028038ce4c0c807bee4b0bcdd1797bb496 (commit)
       via  cbc0323ace90320d137850792db0114a008042a3 (commit)
      from  2db1f1ebfa37b028ea236ebd1dbc7d617609ce60 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit aa56e9028038ce4c0c807bee4b0bcdd1797bb496
Merge: 2db1f1ebfa37b028ea236ebd1dbc7d617609ce60 cbc0323ace90320d137850792db0114a008042a3
Author: Phil Carns <carns at mcs.anl.gov>
Date:   Tue Sep 2 17:06:18 2014 -0400

    Merge remote-tracking branch 'origin/master' into dev-modular

-----------------------------------------------------------------------

Summary of changes:
 darshan-test/RELEASE-CHECKLIST.txt |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)


Diff of changes:
diff --git a/darshan-test/RELEASE-CHECKLIST.txt b/darshan-test/RELEASE-CHECKLIST.txt
index aad5f4c..7d4c3bc 100644
--- a/darshan-test/RELEASE-CHECKLIST.txt
+++ b/darshan-test/RELEASE-CHECKLIST.txt
@@ -8,7 +8,7 @@ Notes on how to release a new version of Darshan
 - check for any problems in jenkins nightly builds
 - make sure that documentation in darshan-util/doc/ and darshan-runtime/doc/
   are up to date
-- update the Changelog if needed (browse svn log since last release)
+- update the Changelog if needed (browse git log since last release)
   - commit
 - update version number in configure.in (see AC_INIT)
   - in both darshan-util/ and darshan-runtime/
@@ -16,11 +16,12 @@ Notes on how to release a new version of Darshan
   - commit
 - generate example output files on x86_64, ppc32, and ppc64, commit in
   darshan-test/example-output/ directory
-- use "svn status" and "svn diff" to make sure all changes are committed to
-  trunk
-- make a tag by doing an svn copy from trunk to tags/darshan-<some number>
+- use "git status" to make sure that all changes have been committed and
+  pushed to origin/master
+- make a tag for the release according to instructions at
+  http://git-scm.com/book/en/Git-Basics-Tagging
 - TESTING
-- svn export the tag, tar gzip it
+- export the tag (TODO: document recommended method) and tar gzip it
   - upload .tar.gz file to /mcs/ftp/pub/darshan/releases
 - generate web documentation from asciidoc by running make in
   darshan-util/doc/ and darshan-runtime/doc/ directories


hooks/post-receive
--