[bknr-devel] Merging development branch

[Tchavdar Roussanov]

Hi Hans,

It works for me. I didn't have time to work with bknr lately. I mostly use
SBCL and in order to compile I have to update most of the third party
libraries to their latest or cvs versions.  I use  a custom init.lisp that
first check if I have  the library in  my  asdf  registry  and only if it is
not there pushes the thirdparty path into it. The biggest problem  I have is
with Portableaserve because it is not thread save with sbcl.

Tchavdar

On 10/24/06, Hans Huebner <hans.huebner at gmail.com> wrote:
>
> Hi Tchadvar,
>
> I have moved all my projects to my development branch and I´d be
> interested in making that branch the new trunk.  The problem I see is
> that some of the changes I made with respect to the XML generation are
> incompatible to the trunk version.
>
> I´d propose the following:  I will create a branch from the current
> trunk which is named "legacy" or some such and then move my
> development branch back to the trunk.
>
> Let me know if that would work for you (and if anyone else reading
> this has any thoughts or objections, please shout!).
>
> -Hans
>
> On 10/24/06, Tchavdar Roussanov <troussan at gmail.com> wrote:
> > Hans,
> >
> > You have made a lot of commits to your development branch recently.
> > Including updates to the third party tree. Do you have plans to merge
> these
> > changes to the trunk?
> >
> > Regards,
> >
> > Tchavdar Roussanov
> >
> > _______________________________________________
> > bknr-devel mailing list
> > bknr-devel at common-lisp.net
> > http://common-lisp.net/cgi-bin/mailman/listinfo/bknr-devel
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/bknr-devel/attachments/20061024/b7b1bbb5/attachment.html>