Reverting the staging branch.

Hi all,

Contrary to staging's objective of being a "stable" branch, it currently 
is badly broken.  So, I will make a copy of its current staging in the 
"culprit's" sandbox, and revert staging to a stable state.

Note to David:  I know that SableJIT was also badly broken by this new 
code.  I recommend that you back off the merge, and work with Greg to 
first solve the normal staging merge with latest classpath.

I will, meanwhile, simply merge classpath's official 0.13 code into 
staging (testing that it does not break-the-world, first. ;-)

[I will make sure to actually do the right thing for the culprit's 
sandbox, and base his branch on the 0.13 merged staging].

I know that breakage can happen; so do not consider this as a critic of 
anybody's work.  It's the objective of staging to catch these things 
early, before they hit end users.  Yet, contrary to CVS trunks, staging 
is not supposed to be remain in a "break everybody's build" state once a 
problem is identified.  It is supposed to be either:
a) fixed immediately, if possible, or
b) reverted to last stable state, and work on a fix moved to private 
sandbox.

I am simply applying solution b), as the problem seems difficult to solve.

Etienne

-- 
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

_______________________________________________
SableVM-devel mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB6p2UjyrJi4rH84gRAoJRAJ0Q7o5IqN2Uix+EaqH0UDZPrLJ8sgCfSqPe
4NtdNbLZIxG2fzJALjeK4DE=
=KGCC
-----END PGP SIGNATURE-----