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

RE: Retrieving all revisions with changes present

From: Bagnall, Martin <Martin.Bagnall_at_hmhpub.com>
Date: Wed, 14 Jan 2009 15:43:24 +0000


-----Original Message-----
From: news [mailto:news_at_ger.gmane.org] On Behalf Of Harry Putnam
Sent: 14 January 2009 05:47
To: users_at_subversion.tigris.org
Subject: Retrieving all revisions with changes present

As someone about to switch from cvs to svn, I want to know how to do
something like what I will describe, using svn.

Imagine I've kept tabs on scriptX through many changes and over a fairly
long time. Long enough that I'm in serious doubt when and how certain
changes were made.

Imagine further that I recall using some code in this script way back
when, but I've forgotten the exact syntax and structure of this piece
of code. All I can remember for sure is that when this change was
done I employed some unusual term somewhere... Maybe in a comment.

So I know I used the word `fructification' for some reason and it was
during an addition that was committed but mnths later stripped out.

Now mnths maybe yrs later still, I run into a problem that the old piece
code might really suit.

I have no idea what mnth, maybe not even the year it was committed.

With cvs I was able to write a script that literally unwound every
revision starting with what ever revision number I aimed it at, and
put the entire change on stdout, one revision at a time but
essentially a massive out pouring of text.

My homeboy I script would filter through that with awk, which I could
make retain each revision number until it rolled over, and If I got a
hit on `fructificaiton', awk would spit out the matching version and
the line containing my hit.

Of course from there, I could make cvs spit the entire script for that
revision to study.

With the big difference in subversion of creating a revision for each
change to the entire repository, a file may remain unchanged for any
number of revisions.

So my approach above would lead to massive unnecessary grepping where
the script didn't actually change.

I'm guessing there is some way other than revision numbers to be able to
home in on only those revisions where changes to scriptX were made.
And therefore the possibility of doing something very similar in
subversion using shell tools if need be, but some better way than just
unwinding 19,000 revisions looking for a keyword, when 18,950 are the


To unsubscribe from this discussion, e-mail:


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-14 17:07:28 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.