[Bug 5842] New: Use milliseconds for commit date

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=5842

            Bug ID: 5842
           Summary: Use milliseconds for commit date
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: aklitzing at gmail.com
                CC: mercurial-devel at mercurial-scm.org

I like to request to use milliseconds as a commit timestamp.

We use Review Board for code review and developed a python script that will
create/update review requests from a changeset in server-side. If a
changeset/review request is approved the called hook will allow the push.
Otherwise it will be denied and the review request will be updated if nothing
has changed.

The best workflow is to use the current author and the commit date to recognize
the changeset during commit message changes, "rebase", "amend", "histedit roll"
and all advanced stuff. This works great - even for grafting as it will use the
current date for us.
We know that it isn't 100% - but the script is smart enough that it is 99%. ;-)

The problem is the "maven release plugin" as it will create 3 commits for a new
release and maybe do that in the same second. This is the only blocker for our
workflow as we need to adjust those date manually.

Is it possible to increase the accuracy of the commit date to milliseconds
instead of seconds? That is the format? Unix timestamp?

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