[Bug 4301] New: Amending a changeset should update to the current time

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=4301

          Priority: normal
            Bug ID: 4301
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Amending a changeset should update to the current time
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: faheem at faheem.info
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: evolution
           Product: Mercurial

i think that amending a changeset should update it to the time it was amended.

I've been having a difference of opinion with Jordi on #mercurial about this.
Jordi is of the opinion that since mq does this, we should emulate mq's
behavior. With respect, I don't see why we need to do this.

Bear in mind that the current behavior will lose information by default.
In the case of mq, the time of modification is stored somewhere, at least if
the mq repos is itself a repos. However, if we amend and keep the same time,
then there is no record when the cset was modified.

-- 
You are receiving this mail because:
You are on the CC list for the bug.