Fork of maxima for make it more embeddable.



Rupert Swarbrick <rswarbrick at gmail.com> writes:

> [1:multipart/signed Hide]
> [1/1:text/plain Hide]
> Michael Filonenko <filonenko.mikhail at gmail.com> writes:
>> Goal of fork to provide maxima from quicklisp. Maxima big project and I
>> need community opinion about fork. I am ready to merge my changes with
>> main repo. Only non-mathematical parts were changed by me.
>
> Hmm. Well, a public github fork is a pretty awful way to develop
> features on changing code unless that code is also in github. How are
> you going to incorporate changes to core maxima into your fork without
> rewriting history?

@Rupert: I am not really certain of your meaning here. Git can
accomodate multiple upstream repositories. So long as he has forked
things correctly, he can pull in updates from sourceforge, and merge
these onto his development branch which is on github. This work can be
merged into the sourceforge repository without re-writing anyone's
history -- that is the nice thing about rebasing.

@Michael: I think what Rupert said about preparing a patch set with some
explanation also makes sense. The main developers are quite cautious
about accepting patches, for the good reason that they do not want to be
liable for fixing other folks' mistakes.

Btw, I do like the idea of making Maxima available as a ql library.

-- 
Leo Butler                <l_butler at users.sourceforge.net>
SDF Public Access UNIX System -   http://sdf.lonestar.org