Re: Version control for PicoLisp (2nd wave)
That git-related article was old. Here are some links you may find solid enough: http://nubyonrails.com/articles/five-features-from-mercurial-that-would-make-git-suck-less http://blog.red-bean.com/sussman/?p=116 Sorry for the double reply, but bear with me please (: On Fri, 21 Aug 2009, Henrik Sarvell wrote: Hi all, there's been some discussion in various places, the IRC channel for instance to use some kins of version control system instead of having Alex laboriously, manually inserting changes. I just searched for a Mercurial version of GitHub and found http://bitbucket.org/plans/. PicoLisp is such a small repository that we can go free on either BitBucket or GitHub. Then I randomly ended up at this comparison page: http://www.rockstarprogrammer.org/post/2008/apr/06/differences-between-mercurial-and-git/ After reading that (which I recommend anyone who wants to chime in on this thread do) I realized that maybe Mercurial isn't the right way to go? It all depends on what we see happening in the future. I've never used Git (other than simply downloading code). If Alex will have the time to act as the guy who gets to decide what goes in and not, and wants superior control of that process then GitHub seems to be the way to go. If no one really will have that time and energy then maybe BitBucket is the way to go, I don't know, maybe GitHub will be a better choice either way. Maybe someone more knowledgeable could provide a more nuanced perspective as I'm not a power user of any VCS. /Henrik -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Re: Version control for PicoLisp
On Fri, Aug 21, 2009 at 09:48:57AM +0200, Henrik Sarvell wrote: http://bitbucket.org/plans/. PicoLisp is such a small repository that we can go free on either BitBucket or GitHub. ... Then I randomly ended up at this comparison page: http://www.rockstarprogrammer.org/post/2008/apr/06/differences-between-mercurial-and-git/ In addition, we might want to consider other possibilities. - Jakob Eriksson comes to mind, he once reserved the domain picolisp.org but we did not use it so far. Jakob? - Or Tomas Hlavaty who already started the PicoWiki on his logand.com. Wouldn't it make sense to put these things together? - I could host it on 7fach.de, where the demo apps and this mailing list are running. But if possible I'd like to avoid another task ;-) Cheers, - Alex -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Re: Version control for PicoLisp
I think any kind of private server is overkill for a 250K source, my suggestion then is to go for Google Code. However, someone still needs to set it up. If TC wants to/have the time then I suggest he sets it up on Google code (he seems to be the best qualified here). With Pico on google code I could add my own stuff, such as JSON encoding/decoding, templating, general helper library and robust RSS XML parsing. This is all highly experimental and buggy stuff, that's why I've never bothered having Alex put it there manually (so much is changing in these things all the time). /Henrik On Fri, Aug 21, 2009 at 11:26 AM, Alexander Burgera...@software-lab.de wro= te: On Fri, Aug 21, 2009 at 09:48:57AM +0200, Henrik Sarvell wrote: http://bitbucket.org/plans/. PicoLisp is such a small repository that we can go free on either BitBucket or GitHub. ... Then I randomly ended up at this comparison page: http://www.rockstarprogrammer.org/post/2008/apr/06/differences-between-m= ercurial-and-git/ In addition, we might want to consider other possibilities. - Jakob Eriksson comes to mind, he once reserved the domain =A0picolisp.org but we did not use it so far. Jakob? - Or Tomas Hlavaty who already started the PicoWiki on his logand.com. =A0Wouldn't it make sense to put these things together? - I could host it on 7fach.de, where the demo apps and this mailing =A0list are running. But if possible I'd like to avoid another task ;-) Cheers, - Alex -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=3dunsubscribe -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe