Hi Hèctor, Then what I might recommend is to import the history of apertium-por-cat into (on top of) the history of apertium-pt-ca, and then rename the latter to replace the former. This might take some effort (might need to be done file by file?), and certainly some git foo.
Does anyone have suggestions for how to go about doing this? Btw, I believe nuboro was a GCI student. There may have been a task to convert trunk pairs to use 3-letter codes. But it sounds like it was done tentatively, and not using best practices. -- Jonathan On Thu, Aug 29, 2019, 01:44 Hèctor Alòs i Font <hectora...@gmail.com> wrote: > Hi Jonathan, > > Sure apertium-por-cat is a continuation of the old apertium-pt-ca. There > is a vast amount of fine work in apertium-pt-ca and it can be found in > apertium-por-cat. But I did not create apertium-por-cat. I found it. It > seems it was created by the user nuboro in January 2016, maybe with the > help of Fran, who also has a commit then ( > https://github.com/apertium/apertium-por-cat/commits/master?after=e918d92eef977808f5542db47c549e27832aa0ed+209 > ). > I think that the problem is "only" with the history of apertium-pt-ca in > GitHub if it is removed. > By the way, the AUTHORS file in apertium-por-cat was empty, which seemed > strange to me. I see now that that AUTHORS file in apertium-pt-ca has a > number of lines, so I am surprised why this particular file in > apertium-pot-cat was not copied from apertium-pt-ca. So I'll add now the > old AUTHORS information to the new package. > > Hèctor > > Missatge de Jonathan Washington <jonathan.n.washing...@gmail.com> del dia > dj., 29 d’ag. 2019 a les 5:59: > >> 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 >> > _______________________________________________ > 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
