How to change a changeset date

[Scott Palmer]

It's nothing that 5 months of procrastination can't fix.

On Fri, Feb 27, 2015 at 9:24 AM, Isaac Jurado <diptongo at gmail.com> wrote:

> On Fri, Feb 27, 2015 at 10:00 AM, Mariska Hoogenboom
> <M.Hoogenboom at nl.ccv.eu> wrote:
> > Hi,
> >
> > One of our developers commited a changeset with a future date (+5
> > months from now) to mercurial and pushed it to the server.
> > Consequently, this future date is also visible on the server and
> > messes up our activity stream in JIRA (via FishEye). Is there anyway
> > to correct the date of a changeset in Mercurial?
>
> You'll have to create the commit again, with the fixed date.  This will
> generate a different commit hash identifier.  And you'll have to strip
> the bogus commit from the server repository and all the clones that
> pulled from it since the bogus commit was pushed.
>
> I've been through that pain and I can only advise you tu configure a
> push hook on the server repositories (the "pretxnchangegroup" hook) and
> do some validation from there.  This is was I ended up doing because
> careful people seem to be in danger of extintion.
>
> Regards.
>
> --
> Isaac Jurado
>
> "The noblest pleasure is the joy of understanding"
> Leonardo da Vinci
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150227/f1712f11/attachment-0002.html>