Hi all,
Can we decide if the following branches have been merged, are useful
enough to be merged, need more work, "maybe one day", are very outdated,
or turned out just to be a plain bad idea? The numbers are the rev
number of the last change.
Also, what about separating in-development branches that we expect to
merge or kill soon, from the branches that are for "some other idea",
e.g. "effect-analysis", which may not be merged in a long while but
still we may want to keep around?
* 71164 abort-no-asm (fijal, cfbolz)
* 70752 bridges-experimental (cfbolz)
* 55732 build-external (amaury)
* 63757 classdeco (benjamin)
* 68723 effect-analysis (verte)
* 55751 eval-loop-experiments (antocuni)
* 68703 gc-arena (arigo)
* 70970 gc-huge-list (fijal, arigo)
* 70689 jit-profiling (pedronis, fijal)
* 55472 judy-trees (fijal)
* 71270 kill-can-inline (cfbolz)
* 49688 newdotviewer (misto)
* 64690 pypycpp (igorto)
* 70786 separate-compilation (amaury)
* 70024 sepcomp (xoraxax)
* 66009 type-celldict (cfbolz)
* 64645 unicode_filename (amaury)
* 70890 unroll-safe-if-const-arg (fijal, cfbolz, arigo)
Interesting to see the wide range of authors :-)
A bientot,
Armin.
_______________________________________________
[email protected]
http://codespeak.net/mailman/listinfo/pypy-dev
