[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] experimental branch
From: |
Christian Kellermann |
Subject: |
Re: [Chicken-hackers] experimental branch |
Date: |
Sat, 25 Jun 2011 21:34:22 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
* felix winkelmann <address@hidden> [110625 21:25]:
> I meant that I will develop directly on master. Only long-term work
> (like "specialization") is intended to be on separate branches. So,
> you will know soon enough when things break. :-)
Ah this is what I was missing. I have misread your original message.
Thanks for the clarification. I love it when things break ;)
This also means that I will switch of the salmonella runs of
experimental on my machine as soon as it is gone. Not that this worked
well, the sync has broken ever since and I always forget to push new
results manually.
> Just use "master" if you are adventurous. The other branches are:
>
> expander-simplifications Peter Bex' branch for expander fixes
> specialization Optimizations based on an enhanced
> scrutinizer
> (soon to be merged)
> fat-symbols[-bootstrap] An experiment to implement "lazy" print-name
> generation for gensyms (disappointing
> results,
> and currently stale)
> irregex-bugfixes Also by Peter Bex for irregex changes
> prerelease Staging branch for development on releases
> release Branch for the next release
> spiffy-debug obsolete
>
> The others I have deleted. No branch is "private", try whatevery you want.
Thanks for that explanation. I always wanted to ask about fat-symbols
but never dared...
Thanks again!
Christian
--
Who can (make) the muddy water (clear)? Let it be still, and it will
gradually become clear. Who can secure the condition of rest? Let
movement go on, and the condition of rest will gradually arise.
-- Lao Tse.