Re: git bisect; finding exact commits of bugs

On Fri, Nov 27, 2009 at 9:27 PM, Graham Percival wrote: > If it doesn't exist already, is it worth writing something for the > CG about using git bisect to find the exact commit where a > regression was introduced? There doesn't appear to be anything in the CG about `git bisect'. The man page fo

git bisect; finding exact commits of bugs

If it doesn't exist already, is it worth writing something for the CG about using git bisect to find the exact commit where a regression was introduced? If it does exist, would it be worth trying to convince a frog or two to spend time doing this? I heartily admit that it's not glamorous work, bu

Re: nifty grid view of issues

On Fri, Nov 27, 2009 at 09:04:10PM -0700, Carl Sorensen wrote: > On 11/27/09 2:29 PM, "Graham Percival" wrote: > > > After a bit of experimenting, I think this is the best way to view issues: > > > > http://code.google.com/p/lilypond/issues/list?mode=grid=Priority=Type=ids > > Yes, quite ni

Re: nifty grid view of issues

On 11/27/09 2:29 PM, "Graham Percival" wrote: > After a bit of experimenting, I think this is the best way to view issues: > http://code.google.com/p/lilypond/issues/list?mode=grid=Priority=Type=ids > ls=ids>

Re: nifty grid view of issues

On Fri, Nov 27, 2009 at 2:29 PM, Graham Percival wrote: > After a bit of experimenting, I think this is the best way to view issues: >     > http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids > > Neat, huh?  I'll add it to the CG. Yes! That is very cool. Somehow t

nifty grid view of issues

After a bit of experimenting, I think this is the best way to view issues: http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids Neat, huh? I'll add it to the CG. Note that anything in the High or Regression range stops 2.14 from being released. BTW, my initi

LSR update adds whitespace

commit d069aeb6109be7dd0f93b1e6b65f79198335ab96 adds a single space at the end of a line to a bunch of files in LSR. I'm not certain if that's related to the recent changes to makelsr.py, or whether Neil automatically stripped out the extra whitespace when committing LSR updates, or what. Cheer

Re: translations

Le vendredi 27 novembre 2009 à 14:38 +, Graham Percival a écrit : > I have no index_xy.html files where _xy is a number. I have no longer such files generated in my build tree with current master, I hope it's still the same for you. > I have > index_abt, index_toc (which we don't want/need

Re: Issue 872 in lilypond: Changes split-page has broken images

Le lundi 09 novembre 2009 à 20:08 +, Graham Percival a écrit : > And we could try looking into why we get the duplicate > anchors which confuse opera) If Opera is case-sensitive for anchors, it looks like I accidentally solved this issue: this isn't a consequence of a deliberate design but of

Re: [frogs] Frog's Lament

Hi Valentin, On Fri, Nov 27, 2009 at 10:36 AM, David Kastrup wrote: Remember Rune. I feel deeply shocked by your last sentence. Given his prior behavior on the list(s) — how rude and completely lacking in social filters he clearly is — I had honestly thought that nothing else David wou

Re: translations

On Fri, Nov 27, 2009 at 11:32:04AM +0100, John Mandereau wrote: > Le vendredi 27 novembre 2009 à 00:20 +, Graham Percival a écrit : > > I'm really, *really* doubting this. I've got plenty of > > name.fr.html files, and no index_xy.html files. > > I can provide you a SSH access to my box (pro

Re: [frogs] Frog's Lament

On Fri, Nov 27, 2009 at 10:36 AM, David Kastrup wrote: > Remember Rune. I feel deeply shocked by your last sentence. Regards, V. Villenave. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: translations

Le vendredi 27 novembre 2009 à 00:20 +, Graham Percival a écrit : > If you're talking about line 370 and onwards in > web-texi2html.init, then they're already "removed" -- see the > if (0 and ...) > line? They should not be removed, because proper working of translations use functionnality

Re: [frogs] Frog's Lament

Han-Wen Nienhuys writes: > I have a different viewpoint. I am mystified by the desire of some > people to mess with the most complicated parts of the program, without > having the knowledge to pull that. It's possible to do that, but it > requires a lot of skill in absording a lot of code quick

Re: [frogs] Frog's Lament

Graham Percival schrieb: On Thu, Nov 26, 2009 at 10:56:05AM +0100, Marc Hohl wrote: Well documented code is crucial in such a project for other developers to jump on the train, so learning by RTF code isn't fun (as mentioned elsewhere) - for me, it's annoying, it's frustrating, and it keeps m

Re: [frogs] Frog's Lament

Han-Wen Nienhuys schrieb: [...] There is not a goal per se to move stuff from C++ to Scheme, but rather to expose relevant (C++) interfaces to Scheme so people can write the extensions in Scheme if they want. Come to think of it, it's actually a neat project to write a Scheme interface to engra

Re: [frogs] Frog's Lament

Trevor Daniels schrieb: Carl Sorensen wrote Thursday, November 26, 2009 4:31 PM [...] While I was learning how to use the Internals Reference manual I wrote chapter 4 of the Learning Manual to make it easier for others to follow. It also benefitted me: having to write down what I was learning

Re: [frogs] Frog's Lament

Carl Sorensen schrieb: On 11/26/09 2:56 AM, "Marc Hohl" wrote: [...] Two things come to mind here: 1) When any of us asks a question on the list and gets an answer, we ought to add it to the CG. We can either do it by writing a patch, or by writing some text that will get added to