Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 138902 - CVS synchronize operation marks file as 'edited'
Summary: CVS synchronize operation marks file as 'edited'
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: All Windows XP
: P1 major (vote)
Target Milestone: 3.2 RC2   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-27 09:25 EDT by moran CLA
Modified: 2006-05-19 08:26 EDT (History)
1 user (show)

See Also:

Attachments
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 moran CLA 2006-04-27 09:25:47 EDT 
When CVS watch/edit is configured to 'Send a CVS edit notification to the server', and a synchronization is done either with override+update or update, the source is marked as 'edited' (viewable in the Teame->Show Editors). In previous versions (prior 3.2M4 for example) this wan't the case. ONLY when a file was modified it was marked as 'edited', and sent a notification to the server. This ensures that other editors get a notification when editing a shared file.
Comment 1 Bogdan Gheorghe CLA 2006-04-27 11:51:42 EDT 
Fixed in HEAD
Comment 2 moran CLA 2006-04-30 09:10:25 EDT 
verified with 3.2RC2
Comment 3 Hendrik Ebel CLA 2006-05-19 02:25:15 EDT 
Error exists in RC4 too.
Our project is no set to "enable watch/edit for this projec". Only a few binary files are set to watch/edit on CVS. If synchronization is done either with override+update or update, the source is marked as 'edited'. If checkout file e.g. with replace latest from head the file is not set 'edited' as expected.
Comment 4 Michael Valenta CLA 2006-05-19 08:07:28 EDT 
Could you open a separate bug report comment 3? It is a specialized case of the original problem.
Comment 5 Hendrik Ebel CLA 2006-05-19 08:26:35 EDT 
(In reply to comment #4)
> Could you open a separate bug report comment 3? It is a specialized case of the
> original problem.

ok, new bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=142728