On Thu, Feb 2, 2012 at 7:41 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Result of conversion of ancient history from other SCMs, and output from > other third-party tools, can record timestamps that predates inception of > Git. They can cause "git am", "git rebase" and "git commit --amend" to > misbehave, because the raw git timestamp e.g. > > author <a.u.thor@xxxxxxxxxxx> 1328214896 -0800 > > are read from the commit object and passed to parse_date() machinery, As a bit of context: we have some internal tools at Google that create administrative commits that should have no timestamp. I am using "0" and "1" as a deterministic timestamps in these cases (ie. the start of the epoch). While this works well in general, there are some git subcommands that barf on this, causing user-unhappiness. This patch will hopefully resolve these breakages. -- Han-Wen Nienhuys Google Engineering Belo Horizonte hanwen@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html