Re: [Lilypond-auto] Issue 3952 in lilypond: Automatically sort props within each grob-interface.

[lilypond]

Comment #7 on issue 3952 by address@hidden: Automatically sort props within  
each grob-interface.
http://code.google.com/p/lilypond/issues/detail?id=3952

That is _very_ troubling.  "Accidental reverts" in Git are not at all
easy to achieve unless your workflow juggles with directory contents
rather than commits.  In the normal commit-based processes of
cherry-picking, rebasing and merging, it is close to impossible to
accidentally lose a change that already made it into master, unless you
use rather dangerous options (like explicitly using merge strategies
that drop information from one parent).

Can you use

git reflog -p -S key-name-docstr

in your own repository to figure out which operations were responsible
for adding/removing the respective code, then use git reflog around the
indicated commits to see how you got there?

Obviously, we would want to avoid this kind of thing to occur in future.

--
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