On Tue, Nov 11, 2008 at 9:16 AM, Johan Compagner <jcompagner_at_gmail.com> wrote:
>
>>
>> In some cases yes, in others no. It depends what is in the
>> changesets. Changesets are based on revisions. If a single file was
>> changed in revision 8, 9 and 10. It will only show in the changeset
>> for revision 10. So you might be able to update to the revision 8
>> changeset, but it will not include any of the changes for that file.
>
> and that is a pitty
> Why not update that file also to revision 8 and later on if i come to the
> other changeset that has rev 10
> do the update to 10?
>>
>>
>> Likewise, it would not be possible to get the changes that happened in
>> revision 10 without also getting the ones that happened in revisions 8
>> and 9.
>
> Yes i get this, i can understand that this is something that cant be changed
> But it isnt a big problem because when i look at the changes i see them all.
> So i do see them
>
>>
>>
>> The cases where it does work is if revisions 8, 9 and 10 do not share
>> anything in common with each other. Then you can update any of the
>> changesets selectively and it works. As you say, if a folder is
>> included, then all bets are off. You cannot update a folder to r8
>> without also updating everything beneath the folder to that revision
>> as well.
>
> This is also a pitty
> Is it really impossible to only update the propeties of a dir?
> (because that is what i update, the properties so "children" of the dir not
> the dir it self)
>
>
> Problem is for me that i monitor a lot of co workers things. Now i do that
> based
> on changeset and i would lik to have changesets that are really complete as
> possible for that
> specific revision and update only really the files in that changeset and
> nothing more.
> In cvs this was some how easier to manage because the changesets are not so
> mixed up
> and you really update what you see there not suddenly much more.
> So i am just wondering what we could improve in subclise. is everything
> really just subversion
> or can we improve the plugin?
You cannot update a directory without also updating its children. The
Subversion working copy format does not support that concept. CVS
does not version folders so cannot really be used as a comparison. In
our testing of CVS, it handled files the same way that we do (with the
exception of the folder problem). But if a file was changed in many
versions, you do not see the changesets for anything but the latest
version.
I did not write any of this code, but I seem to recall that the
Synchronize view itself, does not allow a file to belong to more than
one changeset. That is why we cannot simply include it in each
changeset. I could be wrong about that. The Subversion API only
tells us the latest version of the file in the repository so there
would be no way to know it belonged to any other revisions anyway, at
least not without running svn log on every file in the view.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-11-11 15:25:29 CET