| Summary: | Replace With Latest from HEAD does not restore file modification date. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jan Skarvall <jan.skarvall> |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.6.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Jan Skarvall
I also just now noticed that the entry for the file in CVS/Entries is updated at the time of replacement, changing the time for the file to be the UTC time of the replacement, e.g.:
/.project/1.3/Thu Mar 31 14:55:04 2011//
---------------------------------- changed time
This seems strange, as the UTC time for the file in CVS/Entries now differs from the UTC time for the same file in the CVS repository.
I can imagine that the observed behavior was meant to cheat CVS to think that the replaced file is up to date with CVS, but I would have preferred that CVS/Entries had not been tampered with, and that the modification time of the replaced file was simply set back to the time in CVS/Entries e.g. by using the touch command or something with similar effect, noting that touch uses local time rather than UTC time. Doing it like this would result in the file having the same modification time as it would have after an import of the project from CVS.
B.t.w. the script uses find ... -newer ... for the check I mention above.
Problem solved! I found out that Team>Revert to Base works exactly as what I was looking for. I did not understand the difference in semantics between Replace With>Latest from HEAD and Team>Revert to Base. (In reply to comment #2) > I did not understand the difference in semantics between Replace With>Latest > from HEAD and Team>Revert to Base. This article should help in case you still have some doubts: http://eclipser-blog.blogspot.com/2007/05/revert-to-base-few-things-about.html |