We use an Allura server hosted on sourceforge.

--
Phil Holmes


----- Original Message ----- From: "Thomas Morley" <thomasmorle...@gmail.com>
To: "Phil Holmes" <m...@philholmes.net>
Cc: "lilypond-user" <lilypond-user@gnu.org>; "Simon Albrecht" <simon.albre...@mail.de>
Sent: Sunday, February 07, 2016 2:15 PM
Subject: Re: Super and sub


2016-02-07 14:50 GMT+01:00 Phil Holmes <m...@philholmes.net>:
I wasn't aware that git-cl "always fails".  Could you describe the problem
and provide a traceback?

I everyone having the same problem?

Well, maybe I confuse something, but I thought we don't use Allura at
all, but sourceforge.net.

Nevertheless, for me it _always_ creates a new entry there (if I enter
nothing when asked for an issue-number)

Cheers,
 Harm


--
Phil Holmes



----- Original Message ----- From: "Simon Albrecht" <simon.albre...@mail.de>
To: "Noeck" <noeck.marb...@gmx.de>; <lilypond-user@gnu.org>
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
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


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


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

Reply via email to