On Mon, May 20, 2013 at 03:45:59PM -0700, Brian Dolbec wrote: > BUT, things are rather slow at getting done at the moment.
jmbsvicetto was talking a while back (last month?) about cutting a new release. Any word on that front? > Personally I think it may be better to wait a bit on the py3 > compatibility changes. Many of the potential problem spots will > need fixing anyway, so conversion would likely be smoother after > some more re-write work is done. This brings the total number of people chomping at the bit to refactor catalyst code up to three‽ There must be something we can do to help unclog the maintenance pipe? > you can get my rewite branch so far at > http://dev.gentoo.org/~dolsen/catalyst/ > > When you clone it, it will compain about not being able to check out > master. You will need to "git checkout re-write". But I would just add > my url as another remote to your current clone and fetch it. Sounds like a job for: git clone --branch rewrite http://dev.gentoo.org/~dolsen/catalyst/ (your branch name doesn't actually have a hyphen ;). FWIW, you can also take a look at my stuff [1]. Cheers, Trevor [1]: http://git.tremily.us/?p=catalyst.git Branch summaries in, for example: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2099/focus=2221 -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
