rebasing multiple git branches at once

I wrote a little shell script to rebase all my local git branches at once. However, reading the git-pull man page makes me wonder if there's not some tragedy waiting to happen. The script is designed for developers who are only tracking the `master' branch (translators shouldn't rebase too casual

Re: `make all' broken?

On 2010-01-23, Patrick McCarty wrote: > On 2010-01-23, Graham Percival wrote: > > On Sat, Jan 23, 2010 at 02:54:16AM -0800, Patrick McCarty wrote: > > > BSTINPUTS=./essay /home/pnorcks/git/lilypond/scripts/build/out/bib2html > > > \ > > > -o ./out/colorado.html \ > > > ./

Re: Make tab-note-heads and fretboards use common code. (issue186268)

Reviewers: Neil Puttock, Message: Neil, Thanks for the careful review. I think I've dealt with everything, but there is still an open question on ly:context-property. As far as I can see, there is not currently a means of putting a default in the ly:context-property call. I can see that it wo

grand-replace.py in CG

Hi Nick, Could you add some info about grand-replace.py to the CG? I'm thinking in the "release work" chapter, in the "administrative policies" section. We might split some of this chapter off into a "general maintenance" chapter, but I'd like to get the info in the CG _somewhere_ before we forg

Re: `make all' broken?

On 2010-01-23, Graham Percival wrote: > On Sat, Jan 23, 2010 at 02:54:16AM -0800, Patrick McCarty wrote: > > BSTINPUTS=./essay /home/pnorcks/git/lilypond/scripts/build/out/bib2html \ > > -o ./out/colorado.html \ > > ./essay/colorado.bib > > > > bibtex: Not writing t

Make tab-note-heads and fretboards use common code. (issue186268)

http://codereview.appspot.com/186268/diff/1/2 File lily/fretboard-engraver.cc (left): http://codereview.appspot.com/186268/diff/1/2#oldcode100 lily/fretboard-engraver.cc:100: SCM changes = get_property("chordChanges"); get_property ( http://codereview.appspot.com/186268/diff/1/2#oldcode101 lily

Re: PATCH: Use same fret-assignment code for FretBoards and TabStaff

Hi Carl, On 22 January 2010 03:14, Carl Sorensen wrote: > Please review the patch at > > http://codereview.appspot.com/186268/show I'll post some comments on Rietveld soon. Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://

Re: compiling confusion (task cycles)

On 1/23/10 6:34 AM, "Carl Sorensen" wrote: > > > > > On 1/22/10 11:45 PM, "Mark Polesky" wrote: > >> Carl Sorensen wrote: >>> I've never used make test-redo or make test-clean. I'd >>> like to have some clarification on what they're used for. >> >> I could be wrong, but it looks like `

Re: compiling confusion (task cycles)

On 1/22/10 11:45 PM, "Mark Polesky" wrote: > Carl Sorensen wrote: >> I've never used make test-redo or make test-clean. I'd >> like to have some clarification on what they're used for. > > I could be wrong, but it looks like `test-redo' accomplishes > (automatically) what you're doing manual

Re: `make all' broken?

On Sat, Jan 23, 2010 at 02:54:16AM -0800, Patrick McCarty wrote: > BSTINPUTS=./essay /home/pnorcks/git/lilypond/scripts/build/out/bib2html \ > -o ./out/colorado.html \ > ./essay/colorado.bib > > bibtex: Not writing to /tmp/tmpSnvwo5bib2html.blg (openout_any = p)

`make all' broken?

Hi, Compiling from scratch on latest master, I get this output: Compiling /home/pnorcks/git/lilypond/Documentation/out/fdl.texi... /home/pnorcks/git/lilypond/Documentation/out/fdl.texi is up to date. lilypond-book.py (GNU LilyPond) 2.13.12 BSTINPUTS=./essay /home/pnorcks/git/lilypond/scri

Re: [PATCH]: New G clef

Carl Sorensen schrieb: Marc Hohl has worked on a new G clef that is rotated about 1.5 degrees clockwise to improve its balance, as suggested by Jan (see ) A 1200-dpi png is available at http://www.hohlart.de/marc/gcleft

Re: compiling confusion (task cycles)

Le vendredi 22 janvier 2010 à 22:45 -0800, Mark Polesky a écrit : > I could be wrong, but it looks like `test-redo' accomplishes > (automatically) what you're doing manually in your step "run > the individual regression files..." The CG says that it > will "redo files differing from baseline". Ju

Re: compiling confusion (task cycles)

Mark Polesky wrote Saturday, January 23, 2010 6:45 AM Carl Sorensen wrote: My cycle is to [edit source files] make (if needed) You lost me there. How will I know if `make' is needed? If you modify any source files that have to be compiled, essentially the c++ files and their includes a

Re: Working on scheme engravers

Hi Eric I'm a relative newcomer to Lily development too, so it's best to keep these questions and answers on the -devel list. That way others can chip in to correct anything I say that is wrong and suggest alternative and probably better ways of achieving what you want to do. I've tried to answ