Description Philipe Mulet 2001-10-10 21:36:25 EDT

Whenever I attempt to release a whole project, it takes a long time to compute the outgoing changes. 
In some cases, I even know I want to override fully what is on the server, and would be happy with a release no compare.

What I mean is that the release operation should trigger a lazy compare action. It would be fine to simply show me the first affected children
(could be a folder) which I can expand if I do care.

Currently, the comparison is performed until all the leaves, and I can still decide to override conflicting changes all at once (which is fine), so
why then forcing me to get the big penalty upfront when comparing.

NOTES:


JohnA (5/29/2001 11:13:25 AM)
	It isn't comparing any contents, it's just comparing the local workspace with the server to see at a 
	resource granularity what has changed.  This has to happen before you can catchup or release anything,
	because otherwise it doesn't know what to release or load.  We never want to allow releasing without
	first checking if the outgoing change conflicts with changes on the server, so this step is necessary.

Kevinm (5/29/01 3:12:04 PM)
	We should (future) see if this can be sped up though.
	Other thought is that the actual tree filling and comparer opening could be taking time,
	so an optimized (just release if no conflicts) action would be faster.