Closed Bug 301140 Opened 19 years ago Closed 19 years ago

cloning an event changes lastModifiedTime

Categories

(Calendar :: Internal Components, defect)

Product:
Calendar
Component:
Internal Components
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mvl, Assigned: mvl)

Details

Attachments

(1 file)

don't set stamptime
958 bytes, patch
shaver
: first-review+
Details | Diff | Splinter Review 
When cloning an event, the lastModifiedTime of both the original and the clone
are set to the current time.
The original should never change, and i don't thing the clone should change either.
Attached patch don't set stamptime — — Splinter Review 
The problem seems to be that stamptime is changed when cloning. I don't think
it is needed, but vlad added it for full recurrence support. Vlad, is it really
needed? Do you use the stamp anywhere?
Assignee: shaver → mvl
Status: NEW → ASSIGNED
Attachment #189631 - Flags: first-review?(vladimir)
Attachment #189631 - Flags: first-review?(vladimir) → first-review?(shaver)
Comment on attachment 189631 [details] [diff] [review]
don't set stamptime

r=shaver
Attachment #189631 - Flags: first-review?(shaver) → first-review+
patch checked in.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: