Excerpts from Yury G. Kudryashov's message of Thu Aug 12 20:13:34 +0200 2010: > 6. git blame can detect moved lines. At this point I'd say that being able to browse the history is more important than ignoring whitespaces. If you hit a commit named "clean up indentation" you know that you have to search once more. Being able to do that fast is more important than ignoring white spaces in the first place - because changing spaces and moving lines is only one operating of many which should preserve behaviour - meaning you can skip that commit when blaming ..
So if you say "git can do that" - also tell about how often you actually use that feature - because if you don't it looks like "Let me find a feature only this VCS has - even though I'm not using it.." That would be fair - and can help everyone to find the best solution in the end. So how much minutes did this feature save you in the past? How often did you actually use it? Estimations are ok. Thanks Marc Weber _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
