Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.5.1

Request #16952 Enable --summarize switch for diff command
Submitted: 2009-12-27 12:00 UTC Modified: 2009-12-30 23:17 UTC
From: dplehati Assigned: mrook
Status: Closed Package: VersionControl_SVN (version 0.3.3)
PHP Version: Irrelevant OS:
Roadmaps: 0.3.4    
Subscription  


 [2009-12-27 12:00 UTC] dplehati (Davor Plehati)
Description: ------------ Enable --summarize switch to $valid_switches for diff command. This would enable users to get a list of changes between two revisions. example usage in cli: svn diff --summarize -r 123:HEAD svn://example.svn.org Best regards, Davor

Comments

 [2009-12-27 22:28 UTC] mrook (Michiel Rook)
-Status: Open +Status: Assigned -Assigned To: +Assigned To: mrook
 [2009-12-27 22:50 UTC] mrook (Michiel Rook)
-Status: Assigned +Status: Closed
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.
 [2009-12-27 23:13 UTC] dplehati (Davor Plehati)
Saw your commit ... I was wondering shouldn't the new 'summarize' switch be defined in VersionControl_SVN_Diff::prepare() and switch-case @line 347 ? Sorry, next time I'll provide a patch :) Thx for a quick reply. Regards, Davor
 [2009-12-28 08:49 UTC] dplehati (Davor Plehati)
-Status: Closed +Status: Open
 [2009-12-28 08:54 UTC] mrook (Michiel Rook)
You are right, I typed 'svn commit' too quickly :)
 [2009-12-30 23:17 UTC] mrook (Michiel Rook)
-Status: Assigned +Status: Closed -Roadmap Versions: +Roadmap Versions: 0.3.4
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.