lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [translations] Re: Working repo


From: Jonas Hahnfeld
Subject: Re: [translations] Re: Working repo
Date: Thu, 04 Mar 2021 18:55:14 +0100
User-agent: Evolution 3.38.4

Am Donnerstag, dem 04.03.2021 um 15:25 +0100 schrieb Jean-Charles
Malahieude:
> Le 04/03/2021 à 14:52, Dénes Harmath a écrit :
> > Hi,
> > 
> > thanks for notifying me of the change, I wasn’t aware at all. I
> > successfully signed up for GitLab, forked the project and created a
> > MR: https://gitlab.com/lilypond/lilypond/-/merge_requests/675
> > Who should be the reviewer for translation MRs?
> > 
> 
> Either myself or Jonas?

MRs to the translation branch won't work because there are no CI
pipelines defined, but I've configured GitLab to require that prior to
merging. So far, we've mostly continued with the practice that
translators have access to the repository and just push the translation
branch.
Now that we have the MR system fleshed out and sufficiently fast
runners, I think it might be time to retire the translation branch:
Translators would open regular MRs that are merged to master, but
outside of the countdown process. That would also allow "outside"
contributors to work on the translation more easily (cf. !668).

> BTW, you have overlong lines! If you use emacs as editor, you could do
> 
> C-x f 72
> 
> 
> to automatically split at 72 characters.

Yes, please fix.
The more immediate problem right now is that Savannah is ahead of
GitLab, so once somebody pushes to GitLab the synchronization will fail
because branches cannot be force-pushed to Savannah. Given the issue
with overlong lines, maybe it's best to reset Savannah's translation
branch to the commit on GitLab? I can do this manually if nobody
disagrees.

Jonas

> 
> Cheers,
> --
> Jean-Charles

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]