On Wed, 22 May 2019 at 09:47, Antony Antony <[email protected]> wrote:
>
> On Tue, May 21, 2019 at 10:44:09AM -0400, Andrew Cagney wrote:
> > Antony,
> >
> > These dates are confusing testing causing it to list 3.27 changes before 
> > 3.28:
>
> This time I know what happened.
>
> I was testing libevent and time jumps, issue Tuomo reported.
> And accidently those commits were comitted during my test in with future
> timestamps. Sorry about this. I will be more mindfull about it.

Ah :-)  Thanks.

> > Posted Monday:
> > On Mon, 20 May 2019 at 06:12, Antony Antony <[email protected]> 
> > wrote:
> > >
> > > New commits:
> > > commit 4f5f1e39809d9e73aecc54f759339f241dcc99a0
> > > Author: Antony Antony <[email protected]>
> > > Date:   Wed May 22 18:32:09 2019 +0000
> >
> > but committed Wednesday, which is:
> >   $ date -u
> >   Tue May 21 14:42:58 UTC 2019
> > tomorrow?
>
> simple git log show those in order:) I noticed github would show it in wrong
> order too.
_______________________________________________
Swan-dev mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-dev

Reply via email to