Re: Access request to push to translation

[Han-Wen Nienhuys]

BTW, regarding translations:

I notice that translation work gets merged as

"commit cb1b3c1fb0c1d9dc1fb6fdadb0907c07b8a692e5
Merge: 22eca98efe b47e5def69
Author: Jean-Charles Malahieude <lilyfan@orange.fr>
Date:   Sat Jun 20 17:44:05 2020 +0200

    Merge branch 'master' into translation"


could we flip the merge order? The history view in gitk now makes it
look as if 'translation' is the main development branch, while
'master' gets merged in from the side.

On Sun, Jun 21, 2020 at 12:51 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>
> Am Sonntag, den 21.06.2020, 12:36 +0200 schrieb Francisco Vila:
> > Hello,
> >
> > https://gitlab.com/lilypond/lilypond/-/merge_requests/183
> >
> > I am told that the whole approach of forking and doing a MR et cetera is
> > not the best way to contribute to translations, and that I should just
> > push to translation branch directly on the official repo.
>
> I mean it's not wrong, but I don't think we should make this more
> complicated than needs to be. Code reviews make sense for development
> work, but the translations have done well without (at least from my
> perspective).
>
>
> > May I get that access? Or else, what is the preferred mechanism to
> > perform what I'been doing on translation branch since pretty much always?
>
> Granted to @pacovila. You also had access to Savannah before the
> transition, and I don't see a reason to deny the equivalent level of
> access.
> If you want, you can now press 'Merge' button for the MR above or just
> push the commit to translation manually.
>
> Jonas



-- 
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen