Hi Eugene,
> I have itch to get an update action from history view, but
> it would
> be really better to implement sync view features like commit sets.
> Currently I feel blind looking at svn sync view in incoming changes
> mode, so I have to run svn history for the whole project in
> order to see
> what was going on with the project, but it is not quite the same,
> because I can't run update from history view and it is also show too
> many changes (sync view in cvs show changes from the head up to local
> revision).
What is the difference between an Eclipse "CVS commit set" and a
Subversion
revision? My understanding of commit sets is that they are trying to
add
atomic commit-style functionality on top of an RCS that doesn't have any
concept that changes might affect multiple files. Subversion supports
this
out of the box. Given this, I would much rather work with "the changes
committed by svn in a single revision". But I haven't used Eclipse and
CVS
for a while, so maybe my understanding of commit sets is wrong.
Cheers,
Ian Brockbank
Applications Software Team Leader
e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
scd: ian@scottishdance.net
t: +44 131 272 7145
f: +44 131 272 7001
Received on Tue Jun 21 21:02:41 2005