From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Dan Johnson <computerdruid@gmail•com>,
Peter Vojtek <peter.vojtek@gmail•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: Is there way to set git commit --date to be older than 1970 ?
Date: Thu, 30 Oct 2014 15:11:53 -0700 [thread overview]
Message-ID: <xmqqtx2ltdg6.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141030214852.GB21017@peff.net> (Jeff King's message of "Thu, 30 Oct 2014 17:48:52 -0400")
Jeff King <peff@peff•net> writes:
> I think it would be a nice project to convert git to consistently use
> signed 64-bit times internally, and then everything would Just Work
> going back to the beginning of history. But the demand for such a
> feature has been low enough that nobody has really dug in and tried the
> conversion.
>
> We do also gain some small amount of efficiency by storing commit
> timestamps as 32-bit values. However, those should always be "current"
> times anyway. I think we are really talking about author timestamps
> here (and of course the underlying time-manipulation functions).
There are only three places we store timestamps that matter in the
on-disk representations, so if we were to go 64-bit internally,
which I do not mind at all, we probably should do all three i.e.,
committer, tagger and author dates.
next prev parent reply other threads:[~2014-10-30 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 18:49 Is there way to set git commit --date to be older than 1970 ? Peter Vojtek
2014-10-29 19:19 ` Fredrik Gustafsson
2014-10-29 19:50 ` Peter Vojtek
2014-10-29 19:31 ` Junio C Hamano
2014-10-29 20:03 ` Roberto Eduardo Decurnex Gorosito
2014-10-30 21:08 ` Dan Johnson
2014-10-30 21:48 ` Jeff King
2014-10-30 22:11 ` Junio C Hamano [this message]
2014-10-30 17:24 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtx2ltdg6.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=computerdruid@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
--cc=peter.vojtek@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox