Quote:
Originally Posted by eschwartz
If a bug applies to the brand-new codebase as well, then yes, re-post that issue in the new tracker. Plus it shows you still care. 
If there is relevant discussion in the Marvin 2 tracker, you can copy that too, or link to it. |
Absolutely, that's what I'll do, if it's really necessary. That's going to be a
lot of copying and linking. I simply wanted to ask Kris to reconsider whether it was truly necessary to set up a brand-new GitHub. (To be honest, I don't see the two Marvins as two different apps, although I know that technically, they are.)