Skip to content
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

Merge with 'yuma123'. #1

Open
Dr0m0k opened this issue May 7, 2013 · 1 comment
Open

Merge with 'yuma123'. #1

Dr0m0k opened this issue May 7, 2013 · 1 comment

Comments

@Dr0m0k
Copy link

Dr0m0k commented May 7, 2013

I'm very interested in using your library.
I especially like that you start process of re-branding.
But I'm missing some features like usage of 'autotools', 'anyxml' support, etc.
That present in another YUMA fork, it's called 'yuma123' and you can find it by
following link: http://sourceforge.net/p/yuma123 .
Could you please consider possibility to merge changes from this project?
This process should be pretty straightforward because both projects based on
the same 2.2.5 version of original YUMA library.

@AndrewStoneOpenClovis
Copy link
Member

Hmm... I was not aware of that fork. I'd just deprecate this one in favor
of that one except the name, etc does not make me think they are
necessarily that serious about providing a stable repo for Yuma
derivatives.

Since you clearly want and need these additional tools (and know how they
should behave), would you like to do the merge?

Thanks!
Andrew

On Tue, May 7, 2013 at 8:21 AM, Dr0m0k [email protected] wrote:

I'm very interested in using your library.
I especially like that you start process of re-branding.
But I'm missing some features like usage of 'autotools', 'anyxml' support,
etc.
That present in another YUMA fork, it's called 'yuma123' and you can find
it by
following link: http://sourceforge.net/p/yuma123 .
Could you please consider possibility to merge changes from this project?
This process should be pretty straightforward because both projects based
on
the same 2.2.5 version of original YUMA library.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants