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

Re: How to search between branches (complete)

From: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2007-04-17 21:23:42 CEST

On 4/17/2007 2:32 PM, Les Mikesell wrote:
> Hermann Voßeler wrote:
>
>> I completely agree with you that such a feature could be usable
>> sometimes, esp. if you are exploring a new open source project and just
>> want to learn what was/is going on. Subversion seems inded to have a
>> certain lack of functionality here (but as mentioned above, this is
>> not considered very important).
>>
>> You should note though, that "branching" behaves the same way
>> as "copying" and "renaming" and "moving", so keeping track
>> of "all versions in other branches" is much more difficult
>> as you would mean at first glance.
>
> This is really the same issue that comes up frequently as a difference
> from CVS, in that svn has no way to track 'forward' development after a
> tag copy is made. You can only view the history backwards from the tag
> or branch points. I think the only available solution is to keep all
> important changes merged into the trunk so you have a common point to
> diff against to find changes.

That may be the best solution, but it's certainly not the "only". You
can always look through (or write a program to look through) a verbose
log of the repository to find out what copies have been made and what
has been done to them later. As far as I know, that's what TortoiseSVN
does to produce its "revision graph". (I have to admit I've never found
it very useful: it's too slow.)

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 17 21:24:44 2007

This is an archived mail posted to the Subversion Users mailing list.