Eugene Kuleshov <eu@md.pp.ru> wrote on 08/31/2006 02:21:05 PM:
> Can someone please clarify to me how this change set support will act
> for update action called on the change set nodes and on individual
files?
>
> I have feeling that it probably should not allow to update individual
> files in this mode and also should not allow update change sets that are
> newer then some other not-yet updated change sets in given
> synchronization. This would address concerns Brock raised.
>
> I am not sure yet how to act on conflicts yet. Mark probably has
> bigger experience in this then I have, because I mostly monitoring and
> picking up incoming changes and SVN-hosted projects I am working on are
> not very busy, so I don't see conflicts.
I do not see Synch conflicts as a specific area to worry about. Once we
figure out the normal case of how we want to handle things, I think it
will also handle conflicts. In most cases, a Subversion update will
auto-resolve a Synch conflict, if it doesn't it will just produce a local
conflict.
I put some thoughts on update in the issue, email on tigris is just
horribly slow today.
I think that if we always update the items that are specifically in the
synch view, then we can worry less about what is being updated. The
problem then becomes folders getting out of date. What we need is a way
to show out of date folders in the synch view. Then the update processing
will process them.
I guess the biggest problem is that whenever a folder is updated, the
folder (and all of its files) will be updated. This does open the door
for some problems that CVS did not have to worry about.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Aug 31 21:11:11 2006