Hi Hèctor, Do I understand that apertium-por-cat is not a continuation of the code from apertium-pt-ca?
I would have expected that the code is a continuation (or branch) of the old repo. If this were the case, pushing the new code to the apertium-pt-ca repo and renaming it to apertium-por-cat would be the ideal approach. If instead we're dealing with two separate and unrelated code bases (what it sounds like), then we need to figure out a way to keep the old code around but make sure people don't try to use it for anything unless they know that it's been superseded. A two-repo solution is not ideal in this case... -- Jonathan ср, 28 авг. 2019 г. в 08:55, Kevin Brubeck Unhammer <unham...@fsfe.org>: > Hèctor Alòs i Font <hectoralos-re5jqeeqqe8avxtiumw...@public.gmane.org> > čálii: > > > Thanks, Kevin! > > About the other question, I have no idea, but the case of apertium-ca-it > > (which has to be substitued by apertium-cat-ita) is the same. I cannot > > understand has has been done with it: > > https://github.com/search?q=apertium-ca-it > > It seems that ca-it has been *renamed* cat-ita, so now > https://github.com/apertium/apertium-ca-it redirects to > https://github.com/apertium/apertium-cat-ita > > > By the way, apertium-por-cat should probably be labeled as trunk. > > done :) > _______________________________________________ > Apertium-stuff mailing list > Apertium-stuff@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/apertium-stuff >
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
