trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertamarton <>
Subject [GitHub] incubator-trafodion pull request #855: Traf 2357
Date Mon, 28 Nov 2016 19:01:34 GMT
GitHub user robertamarton opened a pull request:

    Traf 2357


You can merge this pull request into a Git repository by running:

    $ git pull traf-2357

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #855
commit e93d518de002f827b8936ddefb59cb04364a9c5a
Author: Roberta Marton <rmarton@edev07.esgyn.local>
Date:   2016-11-22T19:22:25Z

    TRAFODION-2357 log4c++ build error
    There were two problems fixed related to building from a source tar:
    - If you try to build on a node that does not have git installed, then the build
      fails trying to access svn to get the build ID and branch.  Changes were made
      to set the buildID to the current date and to set the branch indicating
      details were unavailable.
    - The problem reported by this JIRA.  Two Makefiles were changed to add an
      INCLUDE to point to the location of log4cxx in the tools directory.

commit 2ff86e80bf6b705016338e72e8084cb937ebb9dd
Author: Roberta Marton <rmarton@edev07.esgyn.local>
Date:   2016-11-28T17:01:42Z

    Merge branch 'master' into traf-2357

commit 7656dd06f6ef3684c16d2586a69fc6bf27003efb
Author: Roberta Marton <rmarton@edev07.esgyn.local>
Date:   2016-11-28T18:13:17Z

    TRAFODION-2357 log4c++ build error - fixed typo

commit d474c6785f438c854b243e283dcc2f74c8b9322a
Author: Roberta Marton <rmarton@edev07.esgyn.local>
Date:   2016-11-28T19:00:33Z

    Merge branch 'master' into traf-2357


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message