Re: GitLab review email

2020-05-12 Thread Federico Bruni
Il giorno mar 12 mag 2020 alle 15:52, Thomas Morley ha scritto: Am Di., 12. Mai 2020 um 14:23 Uhr schrieb James : Hello On 12/05/2020 13:09, Federico Bruni wrote: > > Il giorno mar 12 mag 2020 alle 07:40, Dan Eble ha > scritto: >> Rietveld used to send email to lilypond-devel for

Re: GitLab review email

2020-05-12 Thread Thomas Morley
Am Di., 12. Mai 2020 um 14:23 Uhr schrieb James : > > Hello > > On 12/05/2020 13:09, Federico Bruni wrote: > > > > Il giorno mar 12 mag 2020 alle 07:40, Dan Eble ha > > scritto: > >> Rietveld used to send email to lilypond-devel for all comments by > >> default, though one could disable that when

Re: GitLab review email

2020-05-12 Thread James
Hello On 12/05/2020 13:09, Federico Bruni wrote: Il giorno mar 12 mag 2020 alle 07:40, Dan Eble ha scritto: Rietveld used to send email to lilypond-devel for all comments by default, though one could disable that when commenting.  Are we satisfied with GitLab's not doing that? I think so b

Re: GitLab review email

2020-05-12 Thread Federico Bruni
Il giorno mar 12 mag 2020 alle 07:40, Dan Eble ha scritto: Rietveld used to send email to lilypond-devel for all comments by default, though one could disable that when commenting. Are we satisfied with GitLab's not doing that? As non developer, I'm satisfied :-) I'm interested in foll

GitLab review email

2020-05-12 Thread Dan Eble
Rietveld used to send email to lilypond-devel for all comments by default, though one could disable that when commenting. Are we satisfied with GitLab's not doing that? — Dan