Le 18/01/2023 à 04:27, David Zelinsky a écrit :
Jean Abou Samra writes:
Le 18/01/2023 à 04:11, David Zelinsky a écrit :
What does this mean?
I did run 'make; make check; make doc' and didn't see any errors. And
the documentation (the only thing I modified) looks good to me.
You need to
Jean Abou Samra writes:
> Le 18/01/2023 à 04:11, David Zelinsky a écrit :
>> What does this mean?
>>
>> I did run 'make; make check; make doc' and didn't see any errors. And
>> the documentation (the only thing I modified) looks good to me.
>
>
> You need to go through the process shown here:
>
Le 18/01/2023 à 04:11, David Zelinsky a écrit :
What does this mean?
I did run 'make; make check; make doc' and didn't see any errors. And
the documentation (the only thing I modified) looks good to me.
You need to go through the process shown here:
https://www.youtube.com/watch?v=s3G0qxwT1
Ok, I forked the main repository, and successfully pushed my new branch
to the fork. But before I could make the merge request, I saw this
email from gitlab:
> Pipeline #750192498 has failed!
>
> Project: LilyPond ( https://gitlab.com/dzcello/lilypond )
> Branch: dev/expand-defineBarLine-documen
David Zelinsky writes:
> Jean Abou Samra writes:
>
>>> But when I go to the Merge Requests page there is no "New Merge
>>> Request" button as the gitlab docs say there should be.
>>
>> For me, there is ... See the screenshot attached.
>
> Not for me. See my attached screenshot.
>
> I did notice
Le 18/01/2023 à 02:05, David Zelinsky a écrit :
Jean Abou Samra writes:
Hi David,
As written privately, please try to write from your address that
is subscribed to this list (d...@dedekind.net) or to subscribe this
one. Otherwise, each of your messages needs to be manually approved
by Mark
Jean Abou Samra writes:
> Hi David,
>
> As written privately, please try to write from your address that
> is subscribed to this list (d...@dedekind.net) or to subscribe this
> one. Otherwise, each of your messages needs to be manually approved
> by Mark or me and doesn't reach the list before th
Hi David,
As written privately, please try to write from your address that
is subscribed to this list (d...@dedekind.net) or to subscribe this
one. Otherwise, each of your messages needs to be manually approved
by Mark or me and doesn't reach the list before this.
Le 18/01/2023 à 00:45, David Z
Jean Abou Samra writes:
> Here is what the contributor's guide has to say on commit access:
>
> https://lilypond.org/doc/v2.24/Documentation/contributor/commit-access
>
> “Generally, only contributors who have already provided a number of
> patches which have been merged to the main repository wi
Le 17/01/2023 à 09:13, Lukas-Fabian Moser a écrit :
Hi David,
Am 17.01.23 um 06:18 schrieb David Zelinsky:
Thanks. As I understand it I will need to first request and be granted
commit access. Or is there another way, given that I am new and
untested?
Welcome - it's great you want to contri
Hi David,
Am 17.01.23 um 06:18 schrieb David Zelinsky:
Thanks. As I understand it I will need to first request and be granted
commit access. Or is there another way, given that I am new and
untested?
Welcome - it's great you want to contribute!
What's being "tested" is mainly your merge req
Dan Eble writes:
> On Jan 16, 2023, at 16:26, David Zelinsky wrote:
>> Or try to make a merge request?
>
> Welcome. This is the way.
Thanks. As I understand it I will need to first request and be granted
commit access. Or is there another way, given that I am new and
untested?
-David
On Jan 16, 2023, at 16:26, David Zelinsky wrote:
> Or try to make a merge request?
Welcome. This is the way.
—
Dan
Hey there developers,
I've been using LilyPond for a few years, and feel it's high time to
give something back. As suggested on the help-us page, I am writing to
ask for guidance.
As background, though I am not a professional programmer, I do have a
lot of coding experience, mostly in conjunctio
14 matches
Mail list logo
