Yeah -- after sending my "oops I'm stupid / RTFM" response, I reviewed
that command. It *is* nice, but doesn't quite do what I was wanting --
an entire history of revisions that changed a section of code.
Anyway -- it would be great if something like that could be done. In
the meantime it looks like one can approximate it with blame in
conjunction with the -r option. It just seems that to an end-user it
would be simpler/faster if you could do what I originally stated.
*********************************
**** Appended by Interlink Electronics. *****
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 12 19:00:50 2004