I see that there are now active github repositories for ABCL. But the common-lisp.net homepage for ABCL still suggests that we get ABCL source from SVN. Should this be changed? thx, r
-----Original-Nachricht----- Betreff: Moved to github? Datum: 2016-09-01T22:11:43+0200 Von: "Robert P. Goldman" <rpgoldman@sift.info> An: "Armed Bear" <armedbear-devel@common-lisp.net>
I see that there are now active github repositories for ABCL. But the common-lisp.net homepage for ABCL still suggests that we get ABCL source from SVN. Should this be changed?
thx, r Hello,
anyone can clone a repo and create a new one at github, Many Projects suffer from this fact. Some days ago someone wrote a Report about code quality in inkscape with an inofficial github repo as reference. Inkscape still uses Launchpad and bazaar. Just my two Cents. Best Regards Stefan
On 01 Sep 2016, at 22:10, Robert P. Goldman <rpgoldman@sift.info> wrote:
I see that there are now active github repositories for ABCL. But the common-lisp.net homepage for ABCL still suggests that we get ABCL source from SVN. Should this be changed?
Depends. SVN will remain the canonical repository for the current release process until we create another one. We plan to create an “official” git <—> svn repository mapping, but right now don’t have the resources necessary. When the current SYS:RUN-PROGRAM work with UIOP completes, and someone sends me a patchset they think is better than the current status quo, I will add that to the ABCL SVN trunk. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."
On 2016/9/2 22:19, Mark Evenson wrote:
On 01 Sep 2016, at 22:10, Robert P. Goldman <rpgoldman@sift.info> wrote:
I see that there are now active github repositories for ABCL. But the common-lisp.net homepage for ABCL still suggests that we get ABCL source from SVN. Should this be changed?
Depends. SVN will remain the canonical repository for the current release process until we create another one. We plan to create an “official” git <—> svn repository mapping, but right now don’t have the resources necessary.
When the current SYS:RUN-PROGRAM work with UIOP completes, and someone sends me a patchset they think is better than the current status quo, I will add that to the ABCL SVN trunk.
Ferada pointed me to a coherent patchset added as [14853][1] [1]: http://abcl.org/trac/changeset/14853 I added asdf 3.1.7.8 as [14854][2] [2]: http://abcl.org/trac/changeset/14854 We intend to release this as part of abcl-1.4 Cool to see some progress on this; thanks for the patches! -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 01 Sep 2016, at 22:10, Robert P. Goldman <rpgoldman@sift.info> wrote:
I see that there are now active github repositories for ABCL. But the common-lisp.net homepage for ABCL still suggests that we get ABCL source from SVN. Should this be changed?
Depends. SVN will remain the canonical repository for the current release process until we create another one. We plan to create an “official” git <—> svn repository mapping, but right now don’t have the resources necessary.
I know that Github allows accessing Git repositories through SVN. Maybe Gitlab can do that too, being a derivative of Github. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
participants (4)
-
Mark Evenson -
Robert P. Goldman -
stefan-husmann＠t-online.de -
Stelian Ionescu