Re: Log excluding svn:mergeinfo changes

I will gladly lend time and energy as available; I envision even more affected commands, such as info and ls for their last committed revision calculation. Thanks, Thomas S. Trias Senior Developer Artizan Internet Services http://www.artizan.com/ Original Message Subject

Re: Best way to capture implicit affected paths for a revision

Stefan, I had thought the same about the diff implementation; I guess it pays to search the issue tracker. I will keep on chugging along until such time as diff is fixed. Thanks, Thomas S. Trias Senior Developer Artizan Internet Services http://www.artizan.com/

Log excluding svn:mergeinfo changes

would be nice to also have options to ignore the property for the purposes of log, info, diff, ls, etc. Maybe this already exists and I'm missing something? Thanks, -- Thomas S. Trias Senior Developer Artizan Internet Services http://www.artizan.com/

Best way to capture implicit affected paths for a revision

Does anyone have any ideas or suggestions on the best way to capture this information? Is there an underlying mechanism to return the complete graph difference for a revision? Thanks, -- Thomas S. Trias Senior Developer Artizan Internet Services http://www.artizan.com/