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

RE: ran get-location-segments.py returns 0

From: Rokhkin, IlyaX <ilyax.rokhkin_at_intel.com>
Date: Sun, 19 Feb 2012 13:37:46 +0000

OK, now I understand
Need to run #get-location-segments.py /repo/path/to/filename
And then it says example if the file foo has 3 other instances in history that were replaced (R)
So get-location-segments.py works per file and not per repo, right?

Ilya Rokhkin
Configuration Management Engineer
Intel - Data, storage and SW Team
iNET: 8-920-6165
Tel: +972-3-9296165

-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: Sunday, February 19, 2012 14:56
To: Rokhkin, IlyaX
Cc: users_at_subversion.apache.org
Subject: Re: ran get-location-segments.py returns 0

On Sun, Feb 19, 2012 at 12:44:55PM +0000, Rokhkin, IlyaX wrote:
> Yes, it helps
> But the issue more complicated
> We have hundred such files in the repo, and we do not know the names, we want to find all those files that were replaced (R)

Well, if you run 'svn log' on the repository root it will list all
commits ever made. So you can find all replaced files this way.

> In collabnet they said me that get-location-segments.py can find all such files in the repo

I think they misunderstood what you want to do. get-location-segments
solves an entirely different problem. It answers "given a file foo,
at which other locations did this file exist in history?". You seem
to be asking "What is the list of paths at which one or more
replacements occured in history?". That's a different problem.
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Received on 2012-02-19 14:38:46 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.