Re: [boost] [serialization] new portable binary archive based, on HDF5
On Fri, 13 Dec 2013 22:39, Mateusz Loskot
My suggestion would be for Robert Ramey and other interested developers to consider the inclusion of my work in the official serialization code. I am not sure about the exact procedure in this case.
I *guess*, it may qualify for the Fast Track Review: http://www.boost.org/community/reviews.html
I will check out the procedure.
I have forked from the Git serialization archive. All supplied tests have passed for gcc on Linux and MSVC 10 on Windows. My work can be pulled from
Hmm, have you updated the development branch with the upstream lately, as well as the master in your fork?
AFAICT it is a few months behind the current upstream, the master too, it seems impossible to generate a diff usable enough to review your additions.
You are right, I have neglected to synchronize with the upstream master, and mostly ignored my own master branch. Please try again now. Best regards, Daniel Koester
On 15 December 2013 08:22, Daniel Koester
On Fri, 13 Dec 2013 22:39, Mateusz Loskot
wrote: I have forked from the Git serialization archive. All supplied tests have passed for gcc on Linux and MSVC 10 on Windows. My work can be pulled from
Hmm, have you updated the development branch with the upstream lately, as well as the master in your fork?
AFAICT it is a few months behind the current upstream, the master too, it seems impossible to generate a diff usable enough to review your additions.
You are right, I have neglected to synchronize with the upstream master, and mostly ignored my own master branch. Please try again now.
You could have used git rebase [1]. Anyway, comparing only your commits since Aug 18, 2013 onwards seems working fine. [1] explanation long: https://blogs.atlassian.com/2013/07/git-upstreams-forks/ short: http://robots.thoughtbot.com/keeping-a-github-fork-updated Best regards, -- Mateusz Ĺoskot, http://mateusz.loskot.net
participants (2)
-
Daniel Koester
-
Mateusz Loskot