New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add travis targets #246

Merged
merged 2 commits into from Feb 4, 2017

Conversation

Projects
None yet
2 participants
@jeroen
Contributor

jeroen commented Feb 4, 2017

No description provided.

jeroen added some commits Feb 3, 2017

@jennybc

This comment has been minimized.

Member

jennybc commented Feb 4, 2017

And thank you again!

@jennybc jennybc merged commit ecc456d into tidyverse:master Feb 4, 2017

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

jennybc added a commit that referenced this pull request Apr 12, 2017

Reconcile our "fork" of libxls with upstream; closes #319 (#329)
* Overwrite our libxls "fork" with current svn "HEAD"

svn2github/libxls@bb84eb9

* Don't clutter this operation with xls2csv.c

* No, do not define DEBUG_DRAWINGS

* Suppress print debugging re: XLS_RECORD_MULRK in xls_addCell()

* Reinstate the fix made in PR #273

Rescues read of last column in xls written by some 3rd party tools

* Reinstate the fixes made in PR #312

* Replace #ifdef AIX with #if defined(_AIX) || defined(__sun)

* _WIN32 handling, don't warn for check re: endian-ness

* Bring print statement into line with code

* Changes re: "flexible array members"

* Whitespace the way libxls likes it

* Match va_start() and va_end(); see #195

* Reinstate asprintf() fix from #246

* Re-mask illegal functions for CMD check

* Possible refactor of cran.h

* Undefine assert before redefining

* Quiet more warnings

These are more harmless than they seem on the surface, because there is lots of code in these files that is inside `#ifdef 0 ... `#endif` blocks and the like.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment