mbaedke
mbaedke
> Would be good to get feedback from the Lucene team for this. Definitely > Maybe the issue of "private" properties can be simplified? Now that I realized that they...
@jsedding Yes, I tried that :)
Addressed @kwin 's suggestions.
@steffenvan, it messes up diffs.
@steffenvan, If you - for example during debugging - compare between revisions to see what has changed and git will always tell you that **everything** did, it's very annoying.
Also we are talking git diff, not git blame, right? I guess you can use git blame in an intermediate step to produce a list of files for the diff,...
> the fact that we don't have one is concerning May I ask what's so critical about that? Also, nobody cares about the GitHub blame view. People want to use...
> to me that also sounds like a one time thing. If both revisions have the same formatting, this should not be a problem? Again, if you want to detect...
> Then we backport the code with the new formatting applied? Do you expect cherry-pick to run smoothly in this situation?
> Maybe it's better to move the discussion to the mailing list That makes sense. My Prediction: you will face a lot of resistance :) For (at least) the reasons...