Peter, You should be happy of getting the error message. Since Git 2 invalid years will default to the current year (keeping the given day and month) without warnings. -- Roberto Decurnex On Wed, Oct 29, 2014 at 4:31 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Peter Vojtek <peter.vojtek@xxxxxxxxx> writes: > >> It seems the commit date can be between 1970 and 2100 (on my 32bit >> linux),... > > The underlying data representation records time as number of seconds > since epoch (1970-01-01). Theoretically the codepaths that read > data could consider negative timestamps to represent times before > the epoch, but in the context of source code control, negative > values are more likely to be an indication of a bug or a user > mistake, and I do not think any existing code in Git is prepared to > pass such a timestamp as a sane value---instead they diagnose a > failure and die. > >> I understand that this is rather an esoteric use case :) > > Yeah, this is pretty much outside of what we intend to support. > > Thanks. > > -- > 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 -- 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