cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From karuturi <...@git.apache.org>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-8669: create volume failed due...
Date Fri, 14 Aug 2015 09:19:54 GMT
GitHub user karuturi opened a pull request:

    https://github.com/apache/cloudstack/pull/695

    CLOUDSTACK-8669: create volume failed due to null charset

    Added a new private method getCharSetFromConnection() which checks if
    the connection charset is null and if it is null, returns
    StringUtils.getPreferredCharset
    
    regression caused by commit f03411ca0436c8b52f5e60b0c8820fd1d1ba2ff6

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

    $ git pull https://github.com/karuturi/cloudstack CLOUDSTACK-8669

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

    https://github.com/apache/cloudstack/pull/695.patch

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

    This closes #695
    
----
commit a65339ff1bc99f35fb206f787167ebc98940a829
Author: Rajani Karuturi <rajanikaruturi@gmail.com>
Date:   2015-08-13T12:09:44Z

    CLOUDSTACK-8669: making StringUtils.getDefaultCharset protected
    
    made this protected as its only use is in the Test file.

commit 1dcc5aa7dfaa9e9b3b7f912e1d50fcce41190a3f
Author: Rajani Karuturi <rajanikaruturi@gmail.com>
Date:   2015-08-13T12:22:51Z

    CLOUDSTACK-8669: create volume failed due to null charset
    
    Added a new private method getCharSetFromConnection() which checks if
    the connection charset is null and if it is null, returns
    StringUtils.getPreferredCharset
    
    regression caused by commit f03411ca0436c8b52f5e60b0c8820fd1d1ba2ff6

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message