Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 245509 - Improve extract log
Summary: Improve extract log
Status: RESOLVED FIXED
Alias: None
Product: Subversive
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Alexei Goncharov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-28 06:02 EDT by Alexei Goncharov CLA
Modified: 2011-05-18 06:47 EDT (History)
0 users

See Also:

Attachments
Patch which resolves this problem (19.62 KB, patch)
2008-09-03 10:36 EDT, Igor Burilo CLA 		i.vinnykov: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexei Goncharov CLA 2008-08-28 06:02:12 EDT 
There should not be two logs for extract. The only one log should contain all the changes, including statuses.
Comment 1 Igor Burilo CLA 2008-09-03 10:36:06 EDT 
Created attachment 111585 [details]
Patch which resolves this problem

The patch makes extract behave as described for local operation.
For remote everithing now is just put into the same log without status.
I think you'll improve it.
Comment 2 Alexei Goncharov CLA 2008-09-03 10:53:38 EDT 
I had a look at the patch and I'll apply it.
And I think I have a decision on providing remote statuses to the remote extract operation.
Thank's for the patch.
Comment 3 Alexei Goncharov CLA 2008-09-03 11:28:18 EDT 
So, I've done.
Thank's for the patch.