lilypond-user
[Top][All Lists]
Advanced

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

Re: Super and sub


From: Phil Holmes
Subject: Re: Super and sub
Date: Sun, 7 Feb 2016 13:50:29 -0000

I wasn't aware that git-cl "always fails". Could you describe the problem and provide a traceback?

I everyone having the same problem?

--
Phil Holmes



----- Original Message ----- From: "Simon Albrecht" <address@hidden>
To: "Noeck" <address@hidden>; <address@hidden>
Sent: Sunday, February 07, 2016 1:45 PM
Subject: Re: Super and sub


On 07.02.2016 14:27, Noeck wrote:
Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?

It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially
<http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl>.
Basically, if everything is set up, you do the following:
– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue
and try to create an Allura tracker issue as well, which currently
always fails.
– So you create an issue manually (if you don’t have permission, just
ask on the devel list), linking to the Rietveld issue, with
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and
you don’t have push access, you should send patches (created via ‘git
format-patch HEAD~n’, where n is the number of commits) to James.
For further questions, just ask on the devel list.

Best, Simon

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user




reply via email to

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