From: Trevor Daniels Date: Mon, 8 Feb 2010 13:10:55 +0000 (+0000) Subject: Docs: Contributor: nitpick X-Git-Tag: release/2.13.13-1~15 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=6ed9d0cb39c54ab0a4e8817e2fbde308e7508544;p=lilypond.git Docs: Contributor: nitpick --- diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi index c6a55bcce9..b784bfaccc 100644 --- a/Documentation/contributor/issues.itexi +++ b/Documentation/contributor/issues.itexi @@ -288,9 +288,9 @@ LilyPond, and generally a fair amount of technical knowledge. Even if you are not familiar with git or are not able to compile LilyPond you can still help to narrow down the cause of a regression -simply by downloading the binaries of different LilyPond versions -and testing them for the regression. Knowing which version of -LilyPond first exhibited the regression is helpful to a developer +simply by downloading the binary releases of different LilyPond +versions and testing them for the regression. Knowing which version +of LilyPond first exhibited the regression is helpful to a developer as it shortens the @code{git bisect} procedure described above. Once a problematic commit is identified, the programmers' job is