Submitted a patch and it was added to the wrong rietveld issue

Greetings dev list, I submitted a patch and I am sorry to say that somehow it was added to the wrong issue: https://codereview.appspot.com/54050043 And a new issue (with the wrong title and content) was created in the google code tracker: https://code.google.com/p/lilypond/issues/detail?id=3883

Re: Submitted a patch and it was added to the wrong rietveld issue

Paul Morris writes: > Greetings dev list, > > I submitted a patch and I am sorry to say that somehow it was added to the > wrong issue: > https://codereview.appspot.com/54050043 > > And a new issue (with the wrong title and content) was created in the google > code tracker: > https://code.google.

Re: Submitted a patch and it was added to the wrong rietveld issue

hi Paul, > I submitted a patch and I am sorry to say that somehow it was added to the > wrong issue: > https://codereview.appspot.com/54050043 > > And a new issue (with the wrong title and content) was created in the google > code tracker: > https://code.google.com/p/lilypond/issues/detail?id=3883

Re: Submitted a patch and it was added to the wrong rietveld issue

Sometimes you also need the other way round. When you have started a new branch (e.g. because you have to review your code) or even when you want to submit the same branch from a different computer you have to run git cl issue old-number to associate the branch to an existing issue. HTH Urs "B

Re: Open counterpoint text, thanks to devs

This looks super interesting! Thanks for sharing. Stefaan. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Submitted a patch and it was added to the wrong rietveld issue

Hi Benko, benko.pal wrote >> It seems that my local git branch was still associated with that previous >> issue, the one I had submitted a patch for before. I was using git-cl. > > yes, git-cl associates the rietveld issue permanently to a branch > (in your ~/lilypond-git/.git/config); it seems

Re: Python 3 support

On Sun, Mar 16, 2014 at 04:41:46PM -0400, Julien Rioux wrote: > I think the following would be a good 1-2 punch approach for the > current development cycle: First, upgrade python in GUB and make > sure we can build current dev and stable branches of lilypond from > it. Then bump the python require

Add on-page-greater-than, -less-than (on-the-fly) (issue 74540044)

Reviewers: , Message: Using a different local branch did the trick. -Paul Description: Add on-page-greater-than, -less-than (on-the-fly) Adds two new ready-made procedures for use with the \on-the-fly conditional markup command. They test whether a page is greater than or less than a user-spe