Re: Syncronize and Commit/Update?
Mark Phippard wrote:
>> Synch is not only for previewing updates (including details/diff for
>>every changed file), but also to have aggregated view of outgoing
>>changes, so you can actually see what you about to commit. In my
>>experience it is reducing risks of accident commits and forgotten
>>commits, especially for very large projects/modules.
>The commit dialog shows the list of outgoing changes, so I do not see how
>the Synch view improves upon this that much. You actually just get the
>same commit dialog from the Synch view anyway.
>I realize some people really like the Synch view, I am just not one of
>them. I do not like it with CVS either, but I think our dialogs are better
>than CVS in that they show more info. So I can see more why you would want
>it with CVS.
Is the sync view also supposed to be the primary place for resolving
conflicting changes? I've tried to use it for that but the workflow
seems unreasonably awkward. I've never used the CVS integration so I
have no idea if this this suclipse's fault or if the feature is just
Received on Wed May 18 12:56:10 2005
This is an archived mail posted to the Subclipse Users