I've got what I think is the latest version of Subclipse installed now
(0.9.34), and comparision using it is still very weak.
I can't compare to a specific particular tag or branch, only to the
latest version in svn or to the version I checked out (I'm guessing
that's what "base revision" represents since it has no options).
On 9/14/05, Cris Daniluk <cris.danilu..mail.com> wrote:
> > I guess we're moving into the realm of OT, but it may be relevant too. But
> > doesn't SVN natively use commit sets? I thought Eclipse commit sets were a
> > workaround for CVS's limitations and that there really isn't a need for them
> > in Subclipse.
> >
> Each commit "set" in SVN has the same commit message, so if you want
> to make a bunch of changes, but have different message for each, you
> can't do it all in one commit. Since I might change a class and then
> take a day or two to commit it (because I'm updating dependant code) I
> might forget the commit message. The Eclipse "commit sets" were very
> helpful for this. So, I don't really consider them at all the same
> thing. Others, like you, do though. Personal preference is a bitch!
>
> But yes, very OT :)
>
This archive was generated by hypermail 2.0.0 : Fri Sep 23 2005 - 15:06:57 EDT