Re: [Subclipse-users] Updating changesets in the synchronize view.

On Dec 18, 2007 9:41 AM, Johan Compagner <jcompagner@gmail.com> wrote:
> This behaves differently then with cvs.
>
> If i for example do a synchronize over a project and i do enable change
> sets.
> then i see a commit set from co worker X (rev 10) and another from co worker
> Y. (rev 11)
>
> But i only want to apply the one from co worker Y (rev 11) at that time (i
> reviewed it)
>
> In cvs i if then say update this change set. It really updates only the
> files that are in that change set
> If you do that with SVN everything gets updated to that revision including
> rev 10
> this is because i guess this command is fired:
>
>
> update -r 11 F:/workspace/designer
>
> At revision 11.
>
>
> But thats a bit wrong. what should happen is that only an update is
> triggered for all the files that are really in that changeset
> So i guess you can't update dirs because that would cause a update from
> other revisions
> But thats what a persons expects it expects that only the files he sees now
> in its change set to be updated
> not suddenly also everything from all the change sets that has a revision
> earlier..

It does behave as you want, with the exception that it depends what is
in the changeset. You would need to turn off the "show out of date
folders" feature otherwise, the project root folder will always show
as changed in the highest revision. So an update of that revision will
update the whole project. If you just turn off that preference the
changeset will only show the files that have changed.

You would just want to remember to do a Team > Update on your project
before doing any refactoring so that the folders are all at HEAD.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org