Re: [gentoo-dev] about commits in the future

2018-02-22 Thread Robin H. Johnson
On Wed, Feb 21, 2018 at 09:47:29AM +0100, Fabian Groffen wrote: > Please consider commit 2fb923d758749be609c1daab2a72ad4f1ec4c2a9 > (use something like >git log --pretty=fuller app-emulation/nemu/nemu-1.4.0.ebuild) > > It was made roughly one day in the future. I'm wondering: > 1) is this bad

Re: [gentoo-dev] about commits in the future

2018-02-21 Thread James Le Cuirot
On Wed, 21 Feb 2018 09:59:49 +0100 Patrice Clement wrote: > Every now and then, my commits get rejected from the Gentoo Git > server with an error saying that my clock is behind and that I need > to rewind it. I then run the command `ntpdate europe.pool.ntp.org' to > get my clock synced. Eventual

Re: [gentoo-dev] about commits in the future

2018-02-21 Thread Patrice Clement
Hi Fabian Every now and then, my commits get rejected from the Gentoo Git server with an error saying that my clock is behind and that I need to rewind it. I then run the command `ntpdate europe.pool.ntp.org' to get my clock synced. Eventually, I rebase my latest commits with git and push to the r

[gentoo-dev] about commits in the future

2018-02-21 Thread Fabian Groffen
Please consider commit 2fb923d758749be609c1daab2a72ad4f1ec4c2a9 (use something like git log --pretty=fuller app-emulation/nemu/nemu-1.4.0.ebuild) It was made roughly one day in the future. I'm wondering: 1) is this bad at all? 2) if it is bad (got me confused for another reason) is it technica