Re: [Lilypond-auto] Issue 4036 in lilypond: Patch: Revert "Issue 3978: Merge alignment cleanup"

[lilypond]

Comment #8 on issue 4036 by address@hidden: Patch: Revert "Issue 3978: Merge  
alignment cleanup"
http://code.google.com/p/lilypond/issues/detail?id=4036

Regarding comment #5: the changes in alignment are obviously not  
working "exactly as expected" since the report on the list was because of  
unexpected behavior.

The change to the still documented behavior could be traced back to a  
single commit.  Reverting commits introducing a regression is a pretty  
standard remedy.  This commit was not amicable to reverting on its own, so  
its reversal requires reverting the whole branch.

In order to see whether that is still an option in the current state of  
master, one needs to run patchy which requires an issue report.

The test run has established that a revert is feasible.  Whether it should  
be done depends on whether a proper cure for the regression can be found in  
a reasonable time frame.  Even when a revert is applied, this does not mean  
that the original patch series cannot be resubmitted in a fixed form at a  
later point of time without pressure.

I invested a sizable effort into tracing this regression to its source and  
trying out various ways of reverting it and testing them for feasibility.   
Getting a "WTF?!?" for that is not exactly encouraging quality assurance  
efforts.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings