On Wed, Sep 11, 2013 at 6:19 PM, James <[email protected]> wrote: > Julien, > > I just had a bit of a shock when I ran the test-patchy script - then > realized that I had inadvertently added an extra character before running > the script > > --snip-- > jlowe@jlowe26vm ~/lilypond-extra/patches (master)$ ./test-patches.py ] > issues [3539, 3521, 3473, 3256, 3194, 3192, 3166, 3086, 3056, 3047, 3031, > 3026, 3003, 2998, 2968, 2893, 2830, 2801, 2736, 2683, 2681, 2658, 2647, > 2646, 2594, 2586, 2535, 2474, 2473, 2411, 2368, 2236, 2230, 2207, 2141, > 2091, 2082, 2066, 2026, 2009, 1908, 1434, 1380, 1370, 1351, 1333, 1278, > 1269, 1228, 1107, 1093, 1030, 1005, 990, 971, 822, 694, 657, 601, 539, 355, > 318, 34] > > The interface to test-patches.py allow you to specify a series of issue numbers on the command line. The command-line parameters are passed to a search query on the issue page. The list you are getting is definitely weird, but it matches what the issue page returns for a "id:]" query: http://code.google.com/p/lilypond/issues/list?q=id%3A] I have no idea how that makes senses.
> --snip-- > > ;) > > Thought maybe David had gone on some bug-fix rampage! > > James > Nice! Julien
_______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
