Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub

Comment #4 on issue 980 by pnorcks: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 Since these mirror repos are easy to set up, here is one for GUB too: http://repo.or.cz/w/gub.git -- You received this message because you are listed

Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub

Comment #3 on issue 980 by pnorcks: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 IIRC, we want to host the repos somewhere that doesn't include a username in the URL. For example, GUB's github URL is "http://github.com/janneke/gub

Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub

Comment #2 on issue 980 by john.mandereau: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 I don't follow what is the problem with the Git repo URL. Can't this be sorted out on Savannah? W.r.t different Git hostings I don't see why

Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub

Comment #1 on issue 980 by pnorcks: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 The two lilypads are completely separate codebases. The Windows one is written in C using the Windows API, and the Mac OS X one is written in PyObjC.

Re: Issue 472 in lilypond: collision rest + (accidental/notehead) with beaming

Updates: Owner: --- Comment #1 on issue 472 by percival.music.ca: collision rest + (accidental/notehead) with beaming http://code.google.com/p/lilypond/issues/detail?id=472 (No comment was entered for this change.) Attachments: foo.preview.png 2.2 KB -- You received this me

Re: Issue 409 in lilypond: collision tie and time signature

Updates: Owner: --- Labels: -Priority-Low Priority-High Comment #3 on issue 409 by percival.music.ca: collision tie and time signature http://code.google.com/p/lilypond/issues/detail?id=409 (No comment was entered for this change.) Attachments: foo.preview.png 2.0 KB

Re: Issue 398 in lilypond: collision clef / stem with changing piano staff

Updates: Status: Fixed Owner: --- Comment #1 on issue 398 by percival.music.ca: collision clef / stem with changing piano staff http://code.google.com/p/lilypond/issues/detail?id=398 Fixed at some point, dunno when or why. -- You received this message because you are listed i

Re: Issue 337 in lilypond: collision: \arpeggioUp should increase horizontal space of \arpeggio

Updates: Status: Fixed Owner: --- Comment #1 on issue 337 by percival.music.ca: collision: \arpeggioUp should increase horizontal space of \arpeggio http://code.google.com/p/lilypond/issues/detail?id=337 Fixed due to overall extra space added to the beginning of a bar, I think

Re: Issue 257 in lilypond: collision accent and tuplet bracket

Updates: Owner: --- Labels: -Engraving-nitpick Comment #1 on issue 257 by percival.music.ca: collision accent and tuplet bracket http://code.google.com/p/lilypond/issues/detail?id=257 (No comment was entered for this change.) Attachments: foo.preview.png 2.0 KB -- Y

Re: Issue 45 in lilypond: collision noteheads with four voices

Updates: Owner: --- Labels: -Priority-Low Priority-High Comment #3 on issue 45 by percival.music.ca: collision noteheads with four voices http://code.google.com/p/lilypond/issues/detail?id=45 (No comment was entered for this change.) Attachments: foo.preview.png 1.5

Re: Issue 40 in lilypond: collision glissando accidental (includes workaround)

Updates: Owner: --- Labels: -Priority-Low Priority-Medium Comment #2 on issue 40 by percival.music.ca: collision glissando accidental (includes workaround) http://code.google.com/p/lilypond/issues/detail?id=40 (No comment was entered for this change.) Attachments: foo

Re: Issue 39 in lilypond: collision flag notehead with polyphony

Updates: Owner: --- Labels: -Priority-Low Priority-High Comment #2 on issue 39 by percival.music.ca: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 (No comment was entered for this change.) Attachments: foo.preview.png 1.

Re: Issue 36 in lilypond: collision cresc and kneed beams

Comment #3 on issue 36 by percival.music.ca: collision cresc and kneed beams http://code.google.com/p/lilypond/issues/detail?id=36 sorry, forgot the image. Attachments: foo.preview.png 3.2 KB -- You received this message because you are listed in the owner or CC fields of this issue,

Re: Issue 36 in lilypond: collision cresc and kneed beams

Updates: Owner: --- Labels: -Priority-Low Priority-High Comment #2 on issue 36 by percival.music.ca: collision cresc and kneed beams http://code.google.com/p/lilypond/issues/detail?id=36 With our new definition of "High" as embarrassing, this qualifies. It's not immediately obvi

Re: Issue 502 in lilypond: hairpins bound to spacer notes are aligned on lyrics

Updates: Owner: --- Comment #3 on issue 502 by percival.music.ca: hairpins bound to spacer notes are aligned on lyrics http://code.google.com/p/lilypond/issues/detail?id=502 Well, we can attach other things to s4, so why not the crescendi? In any case, the music definition looks like

Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t

Updates: Owner: --- Labels: Frog Comment #3 on issue 405 by percival.music.ca: tupletBracket not printed despite #'bracket-visibility=##t http://code.google.com/p/lilypond/issues/detail?id=405 Frog: 5 hours? I mean, fundamentally all you need to do is take out the check if th

Re: Issue 314 in lilypond: incorrect ancient \inclinatum spacing

Updates: Owner: --- Comment #2 on issue 314 by percival.music.ca: incorrect ancient \inclinatum spacing http://code.google.com/p/lilypond/issues/detail?id=314 %% the \inclinatum used in the Climacus does not have correct % spacing or % appearance. The top right, and bottom left edge

Re: Issue 428 in lilypond: collision avoidance fails sometimes with simultaneous voices

Updates: Owner: --- Comment #1 on issue 428 by percival.music.ca: collision avoidance fails sometimes with simultaneous voices http://code.google.com/p/lilypond/issues/detail?id=428 (No comment was entered for this change.) Attachments: foo.png 10.1 KB -- You received this

Re: Issue 397 in lilypond: collision pitchedTrill and tie

Updates: Owner: --- Comment #2 on issue 397 by percival.music.ca: collision pitchedTrill and tie http://code.google.com/p/lilypond/issues/detail?id=397 (No comment was entered for this change.) Attachments: foo.preview.png 2.0 KB -- You received this message because you are li

Re: Issue 220 in lilypond: fingering too close to previous note

Updates: Owner: --- Labels: -Engraving-nitpick Comment #4 on issue 220 by percival.music.ca: fingering too close to previous note http://code.google.com/p/lilypond/issues/detail?id=220 (No comment was entered for this change.) Attachments: foo.preview.png 1.3 KB --

Issue 980 in lilypond: separate git repositories for lilypad and/or gub

Status: Accepted Owner: Labels: Type-Other Priority-Medium Maintainability New issue 980 by percival.music.ca: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 It would be nice if we had a separate git repo for lilypad; everything el

Re: Issue 977 in lilypond: GUB build numbers

Comment #1 on issue 977 by percival.music.ca: GUB build numbers http://code.google.com/p/lilypond/issues/detail?id=977 Closely related: scripts/build/create-weblinks-itexi.py should take these build numbers into account. I'm thinking that if it has an internet connection or is given a set o

Re: Issue 954 in lilypond: GUB add temporary patch to lilypond

Updates: Status: Fixed Comment #6 on issue 954 by percival.music.ca: GUB add temporary patch to lilypond http://code.google.com/p/lilypond/issues/detail?id=954 That has been handled with the release/unstable branch, now complete with instructions in the CG. -- You received this messa