Re: GitLab access

2020-05-27 Thread Valentin Villenave
On 5/27/20, Aaron Hill wrote: > I probably could have been (or rather should > be) submitting patches for consideration. Hear hear! But as I said, helping out on the lists is certainly not less worthy as a way of contributing. > I went ahead and linked my GitHub with GitLab, so I am @seraku24 o

Re: GitLab access

2020-05-27 Thread Aaron Hill
On 2020-05-27 1:02 am, Valentin Villenave wrote: On 5/27/20, Aaron Hill wrote: Apologies for hijacking the thread. No apology needed. The link you provided worked for me without needing an account. What level of access are you talking about? Is it something a mere mortal like me (i.e.

Re: GitLab access

2020-05-27 Thread Urs Liska
Am Mittwoch, den 27.05.2020, 10:02 +0200 schrieb Valentin Villenave: > On 5/27/20, Aaron Hill wrote: > > Apologies for hijacking the thread. > > No apology needed. > > > The link you provided worked for me > > without needing an account. What level of access are you talking > > about? > > Is

Re: GitLab access

2020-05-27 Thread Valentin Villenave
On 5/27/20, Aaron Hill wrote: > Apologies for hijacking the thread. No apology needed. > The link you provided worked for me > without needing an account. What level of access are you talking about? > Is it something a mere mortal like me (i.e. someone who is not > currently a collaborator no

GitLab access

2020-05-26 Thread Aaron Hill
On 2020-05-26 4:13 pm, Valentin Villenave wrote: It may indeed be more useful if added to the NR; I’ve just written a patch with that mind: https://gitlab.com/lilypond/lilypond/-/merge_requests/91 BTW Xavier, if you have a GitLab account and whish to gain access to the tracker and patch reviewin