On Tue, Sep 10, 2019 at 08:19:49PM +0300, Diomidis Spinellis wrote:
> > > - Can you think of any non-obvious issues (e.g. backward compatibility,
> > > switch to the Gregorian calendar) I should be aware of?
> >
> > The big question is: what will existing implementations do with a commit
> > obje
On 10-Sep-19 19:26, Jeff King wrote:
On Tue, Sep 10, 2019 at 05:14:53PM +0300, Diomidis Spinellis wrote:
As people use Git to create synthetic commits of code written in the past
[1,2] it becomes important to handle dates before the Unix epoch (1/1/1970).
I see that modern C libraries, Unix kern
On Tue, Sep 10, 2019 at 12:08:34PM -0400, Randall S. Becker wrote:
> My suggestion is a new feature as a patch. See other contributions.
> While you're at this, especially given how extensive this may be given
> the time_t references, it might be useful to examine the end of epoch
> concerns as we
On Tue, Sep 10, 2019 at 05:14:53PM +0300, Diomidis Spinellis wrote:
> As people use Git to create synthetic commits of code written in the past
> [1,2] it becomes important to handle dates before the Unix epoch (1/1/1970).
> I see that modern C libraries, Unix kernels, and tools can handle such
>
On September 10, 2019 10:15 AM, Diomidis Spinellis wrote:
> As people use Git to create synthetic commits of code written in the past
> [1,2] it becomes important to handle dates before the Unix epoch
> (1/1/1970). I see that modern C libraries, Unix kernels, and tools can handle
> such dates. Ho
5 matches
Mail list logo
