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

RE: RE: How to get history of merged-in branches in trunk?

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: 2007-11-20 18:38:51 CET

> -----Original Message-----
> From: Marko Kaening [mailto:mk362@mch.osram.de]
> Sent: Tuesday, November 20, 2007 11:30 AM
> To: users@subversion.tigris.org
> Subject: RE: How to get history of merged-in branches in trunk?
> Wouldn't it be very helpful if there would be a way from
> within svn to include history information of merged-in files
> from other branches as well, or is this impossible?
> On trunk you can't get the FULL history of a file, I guess
> that's not the intention of a developer, isn't it? I mean, if
> I look at changes a file went through I want to see all of
> them, not only the one on trunk, IF POSSIBLE, OF COURSE.

You can get the full history of a file via 'svn log' (just don't use the
--stop-on-copy switch.)

SVN doesn't have merge tracking and true renames, which are sins that
should be rectified in 1.5.

You are probably used to seeing the "FULL" history of a file in a system
like CVS/RCS/ClearCase where each file is stored as an object, which
allows you to see the history of the file on any branch. However, even
that "FULL" history can be rendered incomplete by Evil Twins. In
contrast, SVN follows changeset and directory based paradigms, so each
file object only has one line of ancestry to maintain.

Personally, once I got used to SVN (after 7 years of being a ClearCase
admin,) I no longer cared about seeing the "FULL" history of an object
(aka a Version Tree that encompassed all branches.) All you really care
about is whether Change X made it to branch Y. In other words, Change
Control > Version Control.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 20 18:55:14 2007

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.