Bug 12021 - prepare-ChangeLog doesn't report moved/copied files
Summary: prepare-ChangeLog doesn't report moved/copied files
Status: RESOLVED DUPLICATE of bug 10342
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-28 17:15 PST by David Kilzer (:ddkilzer)
Modified: 2006-12-31 05:52 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Kilzer (:ddkilzer) 2006-12-28 17:15:21 PST
The prepare-ChangeLog script uses 'svn diff' instead of 'svn stat' to get a list of changed files for a ChangeLog entry.  The 'svn diff' command skips moved/copied files unless they've been changed after they were moved.  The best way to fix this is to switch to using 'svn stat'.
Comment 1 Geoffrey Garen 2006-12-28 17:19:22 PST
I think we had been using svn diff because svn stat was orders of magnitude slower. Not sure if that improved with the new svn, though.
Comment 2 David Kilzer (:ddkilzer) 2006-12-28 17:22:21 PST
(In reply to comment #1)
> I think we had been using svn diff because svn stat was orders of magnitude
> slower. Not sure if that improved with the new svn, though.

Yes, I made that change in r14814 (Bug 9395).  However, r15025 (Bug 9570) let you specify a list of files and directories to operate on, which will greatly improve speed when running and helps if you're working on multiple patches in the same working copy.

Comment 3 David Kilzer (:ddkilzer) 2006-12-29 08:43:42 PST
(In reply to comment #1)
> I think we had been using svn diff because svn stat was orders of magnitude
> slower. Not sure if that improved with the new svn, though.

Which new svn?  Was there a change on the server side, or a new svn client?

Comment 4 David Kilzer (:ddkilzer) 2006-12-31 05:52:04 PST

*** This bug has been marked as a duplicate of 10342 ***