On Mon Jun 09 17:13:42 2008, Whiteknight wrote: > On Fri, Jun 6, 2008 at 11:36 PM, Will Coleda via RT > <[EMAIL PROTECTED]> wrote: > > On Tue Nov 27 14:08:00 2007, pmichaud wrote: > >> Today we cleaned up a lot of the unused branches of the > >> Parrot repository. One of the branches that remains is > >> the 'gcm' branch, created by "heimdall" and last updated > >> on 2005-09-13. Supposedly this is an implementation of > >> a generational gc algorithm for Parrot. > >> > >> Although it may be a bit of work because the branch is > >> so old, it may be worthwhile to bring this branch back > >> into the trunk, or conclusively determine that the branch > >> has already been merged into the trunk, or that it's > >> not worth pursing. > >> > >> Pm > > > > Andrew, chromatic, can you answer this question for us? Is the work > being done for SOC this > > semester going to obviate the need to merge this branch back to > trunk? > > the GMC branch is very old, looks like it was last updated to version > 0.2.2 of the parrot repo. Since then, apparently there have been some > significant changes to some central data structures, and some changes > to the architecture. > > Based on what i've seen today, I would venture to say (and chromatic > might have a different opinion of this) that it is not worthwhile to > merge this branch back to trunk. I am going to see if any individual > algorithms or functions can be salvaged from this, but I don't have > high hopes. > > --Andrew Whitworth >
Given this analysis, I'd recommend deleting the branch. Assigning the ticket to Andrew, he can delete the branch (carefully! =) when he's completed his GSOC work. -- Will "Coke" Coleda
