[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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:
  r3: X/Y/Z (from A/B/C)
  r1: A/B/C

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:
  r3: X/Y/Z_at_3 (from A/B/C)
  r1: X/Y/Z_at_1

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?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2429286

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-10 20:06:58 CET

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.