Suggestion: log --same-path
From: Jacob Weber <jacob_at_jacobweber.com>
Date: Thu, 10 Dec 2009 11:06:02 -0800 (PST)
I'd like to get some feedback on a feature idea for Subversion: a flag in the "log" command that causes it to not follow copies, but to continue showing the same path after it sees a copy operation.
Following copies is useful for seeing the changes to a file's content, but sometimes you need to see the changes to a particular path.
For example, say you had two files A/B/C and X/Y/Z at rev 1. Then you deleted X/Y/Z at rev 2. Finally you copied A/B/C to X/Y/Z at rev 3.
If you did a normal "svn log X/Y/Z", it would show you:
There's no way to you to know that there was an earlier version of X/Y/Z. But if you did "svn log --same-path X/Y/Z", it would show you:
This would be a useful complement to the way SVN distinguishes between operative and pegged revisions. A normal "svn log" will only help you find operative revisions. But currently there's no easy way to find a pegged revision for a path, if it's been deleted or replaced by a copy from somewhere else.
What do you guys think? Is this a possibility?
------------------------------------------------------
Please start new threads on the <users_at_subversion.apache.org> mailing list.
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.