On 08/24/2011 05:38 PM, Julian Foad wrote: > Even from a practical POV, the orthogonality is useful. I have a script > that generates a patch file, basically by running "svn diff", but not > quite. I want the files to appear in alphabetical order of their paths, > and I want to output a list of their paths. So my script runs "svn > status" to find out what paths will appear in the diff, and then runs > "svn diff" on one at a time. If it can run "diff --summarize" instead > of "status", then it can be trivially extended to work on repos paths, > where at the moment it only supports WC paths.
heh yeah, you actually gave me that script back in the days, and with lesser tweaks, I use that code all the time to semi-auto-generate my log messages for svn patches :) It's not always precise, but it's easy to spot the errors when reading through the diff (and the errors follow a pattern). It has probably saved me *hours* of copy-pasting function names into log messages by now. I really like it, thank you very much indeed. Oh, have you by any chance made it act super precise by now? That would be a treat. But, I don't really understand, why do you want to semi-auto-generate a log message for already committed revisions? >> [[[ >> $ svn diff --summarize --old=wc/foo/ --new=wc/bar/ >> svn: E200004: Sorry, svn_client_diff5 was called in a way that is not yet >> supported >> svn: E200004: Only diffs between a path's text-base and its working files >> are supported at this time >> ]]] > > Yes, I want us to support that. Ok. ~Neels
signature.asc
Description: OpenPGP digital signature
