newLISP and an SCM?

[kinghajj]

Lutz, do you think that you could start using an SCM (preferably Git) to track changes to newLISP, and hosting a public repo? I'd like to have access to the latest, cutting-edge version of newLISP to help change the code in any way I can, and I think many others would like that, too.

[newdep]

I like the idea, it is actualy already encouraged to change the code

because the code is open.. Now with  'scm' system you could even more stimmulate enhancements..but Lutz ofcourse should stay the manager

on newlisp to protect wild-coding and the philosophy.. But its upto Lutz ;-)

[Lutz]

If anybody has the time and resources to set something up for viewing, that is fine. For the development process itself, I want to stay out of it. In the past people have contributed editing or adding to the latest source distribution, and that has worked very well.

[cormullion]

Heh, count me out of contributing any C changes... :)



I put some newLISP into Google-Code last month. It wasn't too hard to sort out (but not as easy as it should have been), and now I can just type a single command and the latest working version gets uploaded. I think it uses SVN, and - in the Mac world at least - there's plenty of debate about why SVN (or Git) is better or worse eg  (http://www.friday.com/bbum/2007/07/19/git-will-eat-subversions-lunch/">//http://www.friday.com/bbum/2007/07/19/git-will-eat-subversions-lunch/).



That's probably my last sensible contribution on the subject about which I know little... :)

[newdep]

Owww i prefer newlisp code over C .. So I would only contribute in newlisp..

But I could emagine that some people would like to have an uptodate code tree

..but that is indeed time consuming... The way it is done now works very well for me but a SCM could help evolute newlisp into different areas perhpas...

[kinghajj]

http://repo.or.cz/w/newlisp.git">//http://repo.or.cz/w/newlisp.git



Homepage of the newLISP development Git mirror.



If you have Git installed, use this to get the a clone of the repo:

Code Select Expand

git clone git://repo.or.cz/newlisp.git

Then use this in the repo directory to receive updates:

Code Select Expand

git pull

I'll update this whenever Lutz releases a new development version.

[lithper]

king - excellent!



What we need now is to run "newLisp poetry contests", like perl PR people do - i.e. write texts that parse correctly even if do not do anything special. And doubly valued if they do.



No need for obfuscation contests though. Let that remain perl monopoly ;))

[Lutz]

Nice, thanks!

[cormullion]

Good job - I won't be able to resist trying it out now...



And nice to see you back - I thought you had abandoned newLISP for Common Lisp... :)