Thanks for the MR Rafael. I just merged it. Don't worry about opening
an MR against master right now. master is very outdated. The current
branching process is to branch off the previous gnome-3-xx version (so
for example, I branched off gnome-3-34 to create gnome-3-36). I plan on
cleaning up master after 3.36 is done so that we properly branch off
master for each release, like other modules do.

Link

On Sun, 2020-03-08 at 18:17 -0300, Rafael Fontenelle wrote:
> Em dom., 8 de mar. de 2020 às 08:17, Claude Paroz <cla...@2xlibre.net
> > escreveu:
> > Le 08.03.20 à 11:57, Rafael Fontenelle a écrit :
> > > Claude, Link,
> > > 
> > > Em dom., 8 de mar. de 2020 às 07:21, Claude Paroz <
> > > cla...@2xlibre.net> escreveu:
> > > > Yes, that's the reason. D-L is not able to add a new
> > > > translation when
> > > > the language list is inside a file other than LINGUAS.
> > > > 
> > > > Link, would you be able to make the release-notes make process
> > > > use an
> > > > external LINGUAS file for the language list? Would be awesome!
> > > > 
> > > 
> > > I already provided a patch that enables LINGUAS support for
> > > Release
> > > Notes during discussion of Meson port [1], although it was more
> > > like a
> > > workaround. Applying this or any other solution would awesome
> > > indeed.
> > > 
> > > [1] 
> > > https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/8#note_309128
> > 
> > Thanks Rafael for refreshing my memory!
> > 
> > Unless Link disagrees, I would be for you to commit your small
> > workaround patch and see if it works for the various toolchains.
> > 
> > Claude
> > --
> > www.2xlibre.net
> 
> Filed a merge request with a patch that worked for me:
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/18
> 
> This is for gnome-3-36 branch. My intention is to propose the same to
> master branch afterwards.
> 
> Rafael Fontenelle

_______________________________________________
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Reply via email to