On Wed, 2015-03-11 at 17:35 -0400, Ken Brown wrote:
> I've succeeded in making dynamic loading of modules work in clisp on
> Cygwin, and I'll be issuing a new release soon.
Yeah!
> My work was based on the tip of the upstream Mercurial repository, which
> shows a version number of 2.49+ and is
I've succeeded in making dynamic loading of modules work in clisp on
Cygwin, and I'll be issuing a new release soon.
My work was based on the tip of the upstream Mercurial repository, which
shows a version number of 2.49+ and is at revision 15623. So I was
thinking of using 2.49+hg15623 as th
On Mar 11 21:39, Frank Fesevur wrote:
> 2015-03-11 16:45 GMT+01:00 Corinna Vinschen:
> > Are you happy with github? If so, there's no reason to duplicate
> > the repo on sourceware. We can just make the crusty CVS repo R/O.
> >
> > Or, if you rather switch to sourceware, I can mirror your github
2015-03-11 16:45 GMT+01:00 Corinna Vinschen:
> Are you happy with github? If so, there's no reason to duplicate
> the repo on sourceware. We can just make the crusty CVS repo R/O.
>
> Or, if you rather switch to sourceware, I can mirror your github
> repo and then we simply define the sourceware
On Mar 11 16:11, Frank Fesevur wrote:
> 2015-03-10 16:38 GMT+01:00 Corinna Vinschen:
> > I'm happy to inform you that the move of Newlib/Cygwin from the src CVS
> > repository to the new, combined GIT repository is now final.
>
> What is going to be the policy on cygwin-apps CVS repos? Are they
>
2015-03-10 16:38 GMT+01:00 Corinna Vinschen:
> I'm happy to inform you that the move of Newlib/Cygwin from the src CVS
> repository to the new, combined GIT repository is now final.
What is going to be the policy on cygwin-apps CVS repos? Are they
going to be converted to git as well?
I am workin
